Resource cycle methodology

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may wake up, starting at a subframe, based at least in part on a subframe index of a resource cycle and a system frame number (SFN) wraparound offset that accounts for accumulated lengths of a hyper frame. The UE may receive a data burst during the subframe. Numerous other aspects are described.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application claims priority to U.S. Provisional PatentApplication No. 63/366,204, filed on Jun. 10, 2022, entitled“DISCONTINUOUS RECEPTION METHODOLOGY,” and assigned to the assigneehereof. The disclosure of the prior application is considered part ofand is incorporated by reference into this patent application.

INTRODUCTION

Aspects of the present disclosure generally relate to wirelesscommunication and to techniques and apparatuses for handling resourcecycles and other applications.

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency division multipleaccess (FDMA) systems, orthogonal frequency division multiple access(OFDMA) systems, single-carrier frequency division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless network may include one or more base stations that supportcommunication for a user equipment (UE) or multiple UEs. A UE maycommunicate with a base station via downlink communications and uplinkcommunications. “Downlink” (or “DL”) refers to a communication link fromthe base station to the UE, and “uplink” (or “UL”) refers to acommunication link from the UE to the base station. As will be describedin more detail herein, a BS may be referred to as a Node B, a gNB, anaccess point (AP), a radio head, a transmit receive point (TRP), a NewRadio (NR) BS, a 5G Node B, or the like.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent UEs to communicate on a municipal, national, regional, and/orglobal level. New Radio (NR), which may be referred to as 5G, is a setof enhancements to the LTE mobile standard promulgated by the 3GPP. NRis designed to better support mobile broadband internet access byimproving spectral efficiency, lowering costs, improving services,making use of new spectrum, and better integrating with other openstandards using orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/orsingle-carrier frequency division multiplexing (SC-FDM) (also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, aswell as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. As the demand for mobilebroadband access continues to increase, further improvements in LTE, NR,and other radio access technologies remain useful.

SUMMARY

Some aspects described herein relate to a method for wirelesscommunication at a user equipment (UE). The method may include wakingup, starting at a subframe, based at least in part on a subframe indexof a resource cycle and a system frame number (SFN) wraparound offsetthat accounts for accumulated lengths of a hyper frame. The method mayinclude receiving a data burst during the subframe.

Some aspects described herein relate to a UE for wireless communication.The UE may include a memory and one or more processors coupled to thememory. The one or more processors may be configured to wake up,starting at a subframe, based at least in part on a subframe index of aresource cycle and an SFN wraparound offset that accounts foraccumulated lengths of a hyper frame. The one or more processors may beconfigured to receive a data burst during the subframe.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to wake up, starting at asubframe, based at least in part on a subframe index of a resource cycleand an SFN wraparound offset that accounts for accumulated lengths of ahyper frame. The set of instructions, when executed by one or moreprocessors of the UE, may cause the UE to receive a data burst duringthe subframe.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for waking up, startingat a subframe, based at least in part on a subframe index of a resourcecycle and an SFN wraparound offset that accounts for accumulated lengthsof a hyper frame. The apparatus may include means for receiving a databurst during the subframe.

Some aspects described herein relate to a method of wirelesscommunication performed by a UE. The method may include sleeping inassociation with a discontinuous reception (DRX) cycle. The method mayinclude waking up, starting at a subframe, based at least in part on aspecified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.The method may include receiving a multimedia data burst during thesubframe.

Some aspects described herein relate to a method of wirelesscommunication performed by a UE. The method may include sleeping inassociation with a DRX cycle. The method may include waking up, startingat a subframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a DRX time reference SFN, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset. The method may include receiving amultimedia data burst during the subframe.

Some aspects described herein relate to a method of wirelesscommunication performed by a UE. The method may include sleeping inassociation with a resource cycle. The method may include waking up,starting at a subframe, based at least in part on a specified timeoffset that is added to an instance of the resource cycle based at leastin part on a resource cycle number of the resource cycle and a length ofthe resource cycle, where the specified time offset is based at least inpart on a periodicity of multimedia data bursts, and where the resourcecycle number is based at least in part on the specified time offset. Themethod may include receiving a multimedia data burst during thesubframe.

Some aspects described herein relate to a method of wirelesscommunication performed by a network entity. The method may includepreparing for communication with a UE according to a DRX cycle. Themethod may include transmitting, starting at a subframe, a data burstbased at least in part on a specified time offset that is added to an onduration of the DRX cycle based at least in part on a DRX cycle numberof the DRX cycle and a length of the DRX cycle, where the specified timeoffset is based at least in part on a periodicity of multimedia databursts, and where the DRX cycle number is based at least in part on thespecified time offset.

Some aspects described herein relate to a method of wirelesscommunication performed by a network entity. The method may includepreparing for communication with a UE according to a DRX cycle. Themethod may include transmitting, starting at a subframe, a data burstbased at least in part on a specified time offset that is added to an onduration of the DRX cycle based at least in part on a DRX cycle numberof the DRX cycle and a length of the DRX cycle, where the specified timeoffset is based at least in part on a periodicity of multimedia databursts, and where the DRX cycle number is based at least in part on thespecified time offset.

Some aspects described herein relate to a method of wirelesscommunication performed by a network entity. The method may includepreparing for communication with a UE according to a resource cycle. Themethod may include transmitting, starting at a subframe, a data burstbased at least in part on a specified time offset that is added to aninstance of the resource cycle based at least in part on a resourcecycle number of the resource cycle and a length of the resource cycle,where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the resource cyclenumber is based at least in part on the specified time offset, and wherethe resource cycle number is based at least in part on the specifiedtime offset.

Some aspects described herein relate to a UE for wireless communication.The UE may include a memory and one or more processors coupled to thememory. The one or more processors may be configured to cause the UE tosleep in association with a DRX cycle. The one or more processors may beconfigured to wake up the UE, starting at a subframe, based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a length of the DRX cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset. The one or more processors may be configured to receive amultimedia data burst during the subframe.

Some aspects described herein relate to a UE for wireless communication.The UE may include a memory and one or more processors coupled to thememory. The one or more processors may be configured to cause the UE tosleep in association with a DRX cycle. The one or more processors may beconfigured to wake up the UE, starting at a subframe, based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a DRX time reference SFN, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset. The one or more processors may be configured to receive amultimedia data burst during the subframe.

Some aspects described herein relate to a UE for wireless communication.The UE may include a memory and one or more processors coupled to thememory. The one or more processors may be configured to cause the tosleep in association with a resource cycle. The one or more processorsmay be configured to wake up the UE, starting at a subframe, based atleast in part on a specified time offset that is added to an instance ofthe resource cycle based at least in part on a resource cycle number ofthe resource cycle and a length of the resource cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the resource cycle number is based atleast in part on the specified time offset. The one or more processorsmay be configured to receive a multimedia data burst during thesubframe.

Some aspects described herein relate to a network entity for wirelesscommunication. The network entity may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to prepare for communication with a UE according to a DRXcycle. The one or more processors may be configured to transmit,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.

Some aspects described herein relate to a network entity for wirelesscommunication. The network entity may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to prepare for communication with a UE according to a DRXcycle. The one or more processors may be configured to transmit,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.

Some aspects described herein relate to a network entity for wirelesscommunication. The network entity may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to prepare for communication with a UE according to aresource cycle. The one or more processors may be configured totransmit, starting at a subframe, a data burst based at least in part ona specified time offset that is added to an instance of the resourcecycle based at least in part on a resource cycle number of the resourcecycle and a length of the resource cycle, where the specified timeoffset is based at least in part on a periodicity of multimedia databursts, and where the resource cycle number is based at least in part onthe specified time offset, and where the resource cycle number is basedat least in part on the specified time offset.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to sleep in association witha DRX cycle. The set of instructions, when executed by one or moreprocessors of the UE, may cause the UE to wake up, starting at asubframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset. The set of instructions, whenexecuted by one or more processors of the UE, may cause the UE toreceive a multimedia data burst during the subframe.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to sleep in association witha DRX cycle. The set of instructions, when executed by one or moreprocessors of the UE, may cause the UE to wake up, starting at asubframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a DRX time reference SFN, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset. The set of instructions, whenexecuted by one or more processors of the UE, may cause the UE toreceive a multimedia data burst during the subframe.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to sleep in association witha resource cycle. The set of instructions, when executed by one or moreprocessors of the UE, may cause the UE to wake up, starting at asubframe, based at least in part on a specified time offset that isadded to an instance of the resource cycle based at least in part on aresource cycle number of the resource cycle and a length of the resourcecycle, where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the resource cyclenumber is based at least in part on the specified time offset. The setof instructions, when executed by one or more processors of the UE, maycause the UE to receive a multimedia data burst during the subframe.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network entity. The set of instructions, whenexecuted by one or more processors of the network entity, may cause thenetwork entity to prepare for communication with a UE according to a DRXcycle. The set of instructions, when executed by one or more processorsof the network entity, may cause the network entity to transmit,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network entity. The set of instructions, whenexecuted by one or more processors of the network entity, may cause thenetwork entity to prepare for communication with a UE according to a DRXcycle. The set of instructions, when executed by one or more processorsof the network entity, may cause the network entity to transmit,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network entity. The set of instructions, whenexecuted by one or more processors of the network entity, may cause thenetwork entity to prepare for communication with a UE according to aresource cycle. The set of instructions, when executed by one or moreprocessors of the network entity, may cause the network entity totransmit, starting at a subframe, a data burst based at least in part ona specified time offset that is added to an instance of the resourcecycle based at least in part on a resource cycle number of the resourcecycle and a length of the resource cycle, where the specified timeoffset is based at least in part on a periodicity of multimedia databursts, and where the resource cycle number is based at least in part onthe specified time offset, and where the resource cycle number is basedat least in part on the specified time offset.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for sleeping inassociation with a DRX cycle. The apparatus may include means for wakingup, starting at a subframe, based at least in part on a specified timeoffset that is added to an on duration of the DRX cycle based at leastin part on a DRX cycle number of the DRX cycle and a length of the DRXcycle, where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle number isbased at least in part on the specified time offset. The apparatus mayinclude means for receiving a multimedia data burst during the subframe.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for sleeping inassociation with a DRX cycle. The apparatus may include means for wakingup, starting at a subframe, based at least in part on a specified timeoffset that is added to an on duration of the DRX cycle based at leastin part on a DRX cycle number of the DRX cycle and a DRX time referencesystem frame number (SFN), where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.The apparatus may include means for receiving a multimedia data burstduring the subframe.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for sleeping inassociation with a resource cycle. The apparatus may include means forwaking up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an instance of the resource cycle based atleast in part on a resource cycle number of the resource cycle and alength of the resource cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe resource cycle number is based at least in part on the specifiedtime offset. The apparatus may include means for receiving a multimediadata burst during the subframe.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for preparing forcommunication with a UE according to a DRX cycle. The apparatus mayinclude means for transmitting, starting at a subframe, a data burstbased at least in part on a specified time offset that is added to an onduration of the DRX cycle based at least in part on a DRX cycle numberof the DRX cycle and a length of the DRX cycle, where the specified timeoffset is based at least in part on a periodicity of multimedia databursts, and where the DRX cycle number is based at least in part on thespecified time offset.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for preparing forcommunication with a UE according to a DRX cycle. The apparatus mayinclude means for transmitting, starting at a subframe, a data burstbased at least in part on a specified time offset that is added to an onduration of the DRX cycle based at least in part on a DRX cycle numberof the DRX cycle and a length of the DRX cycle, where the specified timeoffset is based at least in part on a periodicity of multimedia databursts, and where the DRX cycle number is based at least in part on thespecified time offset.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for preparing forcommunication with a UE according to a resource cycle. The apparatus mayinclude means for transmitting, starting at a subframe, a data burstbased at least in part on a specified time offset that is added to aninstance of the resource cycle based at least in part on a resourcecycle number of the resource cycle and a length of the resource cycle,where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the resource cyclenumber is based at least in part on the specified time offset, and wherethe resource cycle number is based at least in part on the specifiedtime offset.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, network entity, wireless communication device, and/orprocessing system as substantially described herein with reference toand as illustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages, will be betterunderstood from the following description when considered in connectionwith the accompanying figures. Each of the figures is provided for thepurposes of illustration and description, and not as a definition of thelimits of the claims.

While aspects are described in the present disclosure by illustration tosome examples, those skilled in the art will understand that suchaspects may be implemented in many different arrangements and scenarios.Techniques described herein may be implemented using different platformtypes, devices, systems, shapes, sizes, and/or packaging arrangements.For example, some aspects may be implemented via integrated chipembodiments or other non-module-component based devices (e.g., end-userdevices, vehicles, communication devices, computing devices, industrialequipment, retail/purchasing devices, medical devices, and/or artificialintelligence devices). Aspects may be implemented in chip-levelcomponents, modular components, non-modular components, non-chip-levelcomponents, device-level components, and/or system-level components.Devices incorporating described aspects and features may includeadditional components and features for implementation and practice ofclaimed and described aspects. For example, transmission and receptionof wireless signals may include one or more components for analog anddigital purposes (e.g., hardware components including antennas, radiofrequency (RF) chains, power amplifiers, modulators, buffers,processors, interleavers, adders, and/or summers). It is intended thataspects described herein may be practiced in a wide variety of devices,components, systems, distributed arrangements, and/or end-user devicesof varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network, inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a base station incommunication with a user equipment (UE) in a wireless network, inaccordance with the present disclosure.

FIG. 3 is a diagram illustrating an example of devices designed for lowlatency applications, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of low-latency traffic andpower states, in accordance with the present disclosure.

FIG. 5 illustrates an example of a misalignment of a discontinuousreception (DRX) cycle and extended reality traffic periodicity, inaccordance with the present disclosure.

FIG. 6 illustrates an example of an anchor cycle with a leap DRX cycle,in accordance with the present disclosure.

FIG. 7 illustrates an example of a DRX configuration with dynamic offsetadjustment that supports DRX techniques with non-uniform cycledurations, in accordance with the present disclosure.

FIG. 8 is a diagram illustrating an example of using a short cadencevalue for DRX, in accordance with the present disclosure.

FIG. 9 is a diagram illustrating an example of using a short cadencevalue for DRX for slot positions, in accordance with the presentdisclosure.

FIG. 10 is a diagram illustrating an example of using a short cadencevalue for DRX, in accordance with the present disclosure.

FIG. 11 is a diagram illustrating an example of using different shortcadence values, in accordance with the present disclosure.

FIG. 12 is a diagram illustrating an example of using a short cadencevalue for DRX, in accordance with the present disclosure.

FIG. 13 is a diagram illustrating an example of using a short cadencevalue for DRX, in accordance with the present disclosure.

FIG. 14 is a diagram illustrating an example of a system frame numberwraparound, in accordance with the present disclosure.

FIG. 15 is a diagram illustrating an example of setting a hyper framelength, in accordance with the present disclosure.

FIG. 16 is a diagram illustrating an example of a radio resource control(RRC) configuration for DRX cycles, in accordance with the presentdisclosure.

FIG. 17 is a diagram illustrating an example of aligning DRX cycles anda multimedia periodicity, in accordance with the present disclosure.

FIG. 18 is a diagram illustrating an example associated with using aspecified time offset, in accordance with the present disclosure.

FIG. 19 is a diagram illustrating an example of a disaggregated basestation, in accordance with the present disclosure.

FIG. 20 is a diagram illustrating an example process performed, forexample, by a UE, in accordance with the present disclosure.

FIG. 21 is a diagram illustrating an example process performed, forexample, by a UE, in accordance with the present disclosure.

FIG. 22 is a diagram illustrating an example process performed, forexample, by a UE, in accordance with the present disclosure.

FIG. 23 is a diagram illustrating an example process performed, forexample, by a base station, in accordance with the present disclosure.

FIG. 24 is a diagram illustrating an example process performed, forexample, by a base station, in accordance with the present disclosure.

FIG. 25 is a diagram illustrating an example process performed, forexample, by a base station, in accordance with the present disclosure.

FIG. 26 is a block diagram of an example apparatus for wirelesscommunication, in accordance with the present disclosure.

FIG. 27 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 28 is a diagram illustrating an example of an implementation ofcode and circuitry for an apparatus, in accordance with the presentdisclosure.

FIG. 29 is a block diagram of an example apparatus for wirelesscommunication, in accordance with the present disclosure.

FIG. 30 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 31 is a diagram illustrating an example of an implementation ofcode and circuitry for an apparatus, in accordance with the presentdisclosure.

FIG. 32 is a diagram illustrating an example of leap offset patterns, inaccordance with the present disclosure.

FIG. 33A is a diagram illustrating an example of subframe indices, inaccordance with the present disclosure.

FIG. 33B is a diagram illustrating an example of subframe indices, inaccordance with the present disclosure.

FIG. 34 is a diagram illustrating an example of backward compatibility,in accordance with the present disclosure.

FIG. 35 is a diagram illustrating an example of handling backwardcompatibility, in accordance with the present disclosure.

FIG. 36 is a diagram illustrating an example associated with using anSFN wraparound offset, in accordance with the present disclosure.

FIG. 37 is a diagram illustrating an example of using an SFN wraparoundoffset, in accordance with the present disclosure.

FIG. 38 is a diagram illustrating an example process performed, forexample, by a UE, in accordance with the present disclosure.

FIG. 39 is a diagram of an example apparatus for wireless communication,in accordance with the present disclosure.

FIG. 40 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 41 is a diagram illustrating an example of an implementation ofcode and circuitry for an apparatus, in accordance with the presentdisclosure.

DETAILED DESCRIPTION

Power dissipation of a user equipment (UE), such as an extended reality(XR) device, may be reduced by limiting an amount of time thatprocessing resources of the UE are active for computations and powerconsumption. Some wireless communication systems may a support adiscontinuous reception (DRX) mode. A UE in a DRX mode may transitionbetween a sleep state for power conservation and an active state fordata transmission and reception. The sleep state involves a reduced useof resources (power saving) for receiving or transmittingcommunications. The active state includes an increased use orrestoration of resources for receiving and transmitting communications.The active state for data transmission and reception may be referred toas a DRX “ON-duration.” A DRX cycle may be a time duration that includesa sleep state and an active ON-duration state for a UE. The DRX cyclemay start at the beginning of an ON-duration and end at the beginning ofthe next ON-duration. In some aspects, a DRX cycle may be referred to asa “DRX long cycle”.

However, there are timing mismatches that prevent successful use of DRX.For example, according to one or more aspects, an update rate for the UEmay be, for example, 120 Hz or 60 Hz, thus resulting in a downlinktraffic burst arrival periodicity of 8.333 ms or 16.667 ms,respectively. However, DRX configurations may have one millisecond asthe finest granularity for a DRX cycle, and the start of the ON-durationmay be aligned to millisecond time boundaries. These partial milliseconddifferences may compound with each traffic burst of an XR traffic periodto misalign the DRX cycle and the multimedia traffic periodicity. Forexample, an XR traffic period (times at which XR traffic data burstsarrive) may drift to a middle of a DRX cycle. The mismatch between whenXR traffic bursts arrive and when the UE wakes for ON-durations of theDRX cycle can cause an increase in latency and power consumption,because if an XR traffic burst arrives when the UE is not awake, the XRtraffic burst has to be retransmitted or is lost as a waste of power andsignaling resources.

The techniques described in more detail below improve alignment of DRXcycles and multimedia traffic to reduce mismatches between themultimedia burst traffic and DRX ON-duration times. For example, the UEmay use a wake-up condition to determine when to wake up, which mayinclude adding a specified time offset, which may be a fixed time shift,to an ON-duration (e.g., a next ON-duration) of a DRX cycle. The wake-upcondition may be based at least in part on the subframe number of asubframe, which in one or more aspects may be a subframe of a frameidentified by a system frame number (SFN). The specified time offset maybe added based at least in part on the DRX cycle number and the DRXcycle length of the DRX cycle. In some aspects, a DRX cycle may be aleap cycle that adds a leap offset or an amount of time (e.g., 1 ms) torealign XR traffic bursts with DRX ON-durations. In some aspects, a UEmay be configured with a leap offset pattern that indicates for whichDRX ON-durations that a leap offset is to be applied. A leap offsetpattern may applied be per leap cycle, which may include a quantity ofDRX ON-durations. An anchor cycle may include multiple leap cycles.

According to one or more aspects, a UE may configure a DRX cycle for acadence of the data bursts, such as every 8.33 ms at 120 Hz, but thecadence of the data bursts may be associated with a periodicity of 1000ms. In one or more examples, with a multimedia periodicity of 1000 msand a DRX cycle of 10,240 ms (1024 SFNs per hyper frame at 10 ms each),the hyper frame (formed by a quantity of SFNs, such as 1024 SFNs) of theDRX may be misaligned with a frame of a multimedia server every 10.24seconds. In some aspects, the wake-up condition may account for this SFNwraparound issue where an end of the hyper frame (end of the 1024 SFNs)causes a misalignment of a subframe index and a traffic burst. Forexample, the UE may wake up based at least in part on an SFN wraparoundoffset, which adjusts for the misalignment caused by an end of a hyperframe. As a result, the UE may not miss traffic bursts, andcommunication performance may improve.

While various aspects described herein are applied to examples with DRXcycles, the various aspects described herein may also apply to otherresource cycles.

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. One skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the disclosure disclosed herein, whether implementedindependently of or combined with any other aspect of the disclosure.For example, an apparatus may be implemented or a method may bepracticed using any number of the aspects set forth herein. In addition,the scope of the disclosure is intended to cover such an apparatus ormethod which is practiced using other structure, functionality, orstructure and functionality in addition to or other than the variousaspects of the disclosure set forth herein. It should be understood thatany aspect of the disclosure disclosed herein may be embodied by one ormore elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

While aspects may be described herein using terminology commonlyassociated with a 5G or New Radio (NR) radio access technology (RAT),aspects of the present disclosure can be applied to other RATs, such asa 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100,in accordance with the present disclosure. The wireless network 100 maybe or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g.,Long Term Evolution (LTE)) network, among other examples. The wirelessnetwork 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110 b, a BS 110 c, and a BS 110 d), a user equipment (UE) 120 ormultiple UEs 120 (shown as a UE 120 a, a UE 120 b, a UE 120 c, a UE 120d, and a UE 120 e), and/or other network entities. A base station 110 isan entity that communicates with UEs 120. A base station 110 (sometimesreferred to as a BS) may include, for example, an NR base station, anLTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G),an access point, a transmit receive point (TRP). Each base station 110may provide communication coverage for a particular geographic area. Inthe Third Generation Partnership Project (3GPP), the term “cell” canrefer to a coverage area of a base station 110 and/or a base stationsubsystem serving this coverage area, depending on the context in whichthe term is used.

A base station 110 may provide communication coverage for a macro cell,a pico cell, a femto cell, and/or another type of cell. A macro cell maycover a relatively large geographic area (e.g., several kilometers inradius) and may allow unrestricted access by UEs 120 with servicesubscriptions. A pico cell may cover a relatively small geographic areaand may allow unrestricted access by UEs 120 with service subscription.A femto cell may cover a relatively small geographic area (e.g., a home)and may allow restricted access by UEs 120 having association with thefemto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A basestation 110 for a macro cell may be referred to as a macro base station.A base station 110 for a pico cell may be referred to as a pico basestation. A base station 110 for a femto cell may be referred to as afemto base station or an in-home base station. In the example shown inFIG. 1 , the BS 110 a may be a macro base station for a macro cell 102a, the BS 110 b may be a pico base station for a pico cell 102 b, andthe BS 110 c may be a femto base station for a femto cell 102 c. A basestation may support one or multiple (e.g., three) cells. The terms“eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”,and “cell” may be used interchangeably herein.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of a basestation 110 that is mobile (e.g., a mobile base station). In someexamples, the base stations 110 may be interconnected to one anotherand/or to one or more other base stations 110 or network nodes (notshown) in the wireless network 100 through various types of backhaulinterfaces, such as a direct physical connection or a virtual network,using any suitable transport network.

In some aspects, the term “base station” (e.g., the base station 110) or“network entity” may refer to an aggregated base station, adisaggregated base station, an integrated access and backhaul (IAB)node, a relay node, and/or one or more components thereof. For example,in some aspects, “base station” or “network entity” may refer to acentral unit (CU), a distributed unit (DU), a radio unit (RU), aNear-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-RealTime (Non-RT) RIC, or a combination thereof. In some aspects, the term“base station” or “network entity” may refer to one device configured toperform one or more functions, such as those described herein inconnection with the base station 110. In some aspects, the term “basestation” or “network entity” may refer to a plurality of devicesconfigured to perform the one or more functions. For example, in somedistributed systems, each of a number of different devices (which may belocated in the same geographic location or in different geographiclocations) may be configured to perform at least a portion of afunction, or to duplicate performance of at least a portion of thefunction, and the term “base station” or “network entity” may refer toany one or more of those different devices. In some aspects, the term“base station” or “network entity” may refer to one or more virtual basestations and/or one or more virtual base station functions. For example,in some aspects, two or more base station functions may be instantiatedon a single device. In some aspects, the term “base station” or “networkentity” may refer to one of the base station functions and not another.In this way, a single device may include more than one base station.

The wireless network 100 may include one or more relay stations. A relaystation is an entity that can receive a transmission of data from anupstream station (e.g., a base station 110 or a UE 120) and send atransmission of the data to a downstream station (e.g., a UE 120 or abase station 110). A relay station may be a UE 120 that can relaytransmissions for other UEs 120. In the example shown in FIG. 1 , the BS110 d (e.g., a relay base station) may communicate with the BS 110 a(e.g., a macro base station) and the UE 120 d in order to facilitatecommunication between the BS 110 a and the UE 120 d. A base station 110that relays communications may be referred to as a relay station, arelay base station, a relay, or the like.

The wireless network 100 may be a heterogeneous network that includesbase stations 110 of different types, such as macro base stations, picobase stations, femto base stations, relay base stations, or the like.These different types of base stations 110 may have different transmitpower levels, different coverage areas, and/or different impacts oninterference in the wireless network 100. For example, macro basestations may have a high transmit power level (e.g., 5 to 40 watts)whereas pico base stations, femto base stations, and relay base stationsmay have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of basestations 110 and may provide coordination and control for these basestations 110. The network controller 130 may communicate with the basestations 110 via a backhaul communication link. The base stations 110may communicate with one another directly or indirectly via a wirelessor wireline backhaul communication link.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE 120 may be stationary or mobile. A UE 120 may include, forexample, an access terminal, a terminal, a mobile station, and/or asubscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone),a personal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a laptop computer, a cordlessphone, a wireless local loop (WLL) station, a tablet, a camera, a gamingdevice, a netbook, a smartbook, an ultrabook, a medical device, abiometric device, a wearable device (e.g., a smart watch, smartclothing, smart glasses, a smart wristband, smart jewelry (e.g., a smartring or a smart bracelet)), an entertainment device (e.g., a musicdevice, a video device, and/or a satellite radio), a vehicular componentor sensor, a smart meter/sensor, industrial manufacturing equipment, aglobal positioning system device, and/or any other suitable device thatis configured to communicate via a wireless medium.

Some UEs 120 may be considered machine-type communication (MTC) orevolved or enhanced machine-type communication (eMTC) UEs. An MTC UEand/or an eMTC UE may include, for example, a robot, a drone, a remotedevice, a sensor, a meter, a monitor, and/or a location tag, that maycommunicate with a base station, another device (e.g., a remote device),or some other entity. A wireless node may provide, for example,connectivity for or to a network (e.g., a wide area network such asInternet or a cellular network) via a wired or wireless communicationlink. Some UEs 120 may be considered Internet-of-Things (IoT) devices,and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs120 may be considered a Customer Premises Equipment. A UE 120 may beincluded inside a housing that houses components of the UE 120, such asprocessor components and/or memory components. In some examples, theprocessor components and the memory components may be coupled together.For example, the processor components (e.g., one or more processors) andthe memory components (e.g., a memory) may be operatively coupled,communicatively coupled, electronically coupled, and/or electricallycoupled.

In general, any number of wireless networks 100 may be deployed in agiven geographic area. Each wireless network 100 may support aparticular RAT and may operate on one or more frequencies. A RAT may bereferred to as a radio technology, an air interface, or the like. Afrequency may be referred to as a carrier, a frequency channel, or thelike. Each frequency may support a single RAT in a given geographic areain order to avoid interference between wireless networks of differentRATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120 a and UE120 e) may communicate directly using one or more sidelink channels(e.g., without using a base station 110 as an intermediary tocommunicate with one another). For example, the UEs 120 may communicateusing peer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or amesh network. In such examples, a UE 120 may perform schedulingoperations, resource selection operations, and/or other operationsdescribed elsewhere herein as being performed by the base station 110.

Devices of the wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided by frequency orwavelength into various classes, bands, channels, or the like. Forexample, devices of the wireless network 100 may communicate using oneor more operating bands. In 5G NR, two initial operating bands have beenidentified as frequency range designations FR1 (410 MHz-7.125 GHz) andFR2 (24.25 GHz-52.6 GHz). It should be understood that although aportion of FR1 is greater than 6 GHz, FR1 is often referred to(interchangeably) as a “sub-6 GHz” band. A similar nomenclature issuesometimes occurs with regard to FR2, which is often referred to(interchangeably) as a “millimeter wave” band despite being differentfrom the extremely high frequency (EHF) band (30 GHz-300 GHz) which isidentified by the International Telecommunications Union (ITU) as a“millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics and/or FR2 characteristics, and thus may effectivelyextend features of FR1 and/or FR2 into mid-band frequencies. Inaddition, higher frequency bands are currently being explored to extend5G NR operation beyond 52.6 GHz. For example, three higher operatingbands have been identified as frequency range designations FR4a or FR4-1(52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise,it should be understood that the term “sub-6 GHz” or the like, if usedherein, may broadly represent frequencies that may be less than 6 GHz,may be within FR1, or may include mid-band frequencies. Further, unlessspecifically stated otherwise, it should be understood that the term“millimeter wave” or the like, if used herein, may broadly representfrequencies that may include mid-band frequencies, may be within FR2,FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It iscontemplated that the frequencies included in these operating bands(e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified,and techniques described herein are applicable to those modifiedfrequency ranges.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may sleep in association with a DRX cycle; wake up, starting at asubframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset; and receive a multimedia databurst during the subframe.

In some aspects, the communication manager 140 may sleep in associationwith a DRX cycle; wake up, starting at a subframe, based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a DRX time reference system frame number (SFN), where the specifiedtime offset is based at least in part on a periodicity of multimediadata bursts, and where the DRX cycle number is based at least in part onthe specified time offset; and receive a multimedia data burst duringthe subframe.

In some aspects, the communication manager 140 may sleep in associationwith a resource cycle; wake up, starting at a subframe, based at leastin part on a specified time offset that is added to an instance of theresource cycle based at least in part on a resource cycle number of theresource cycle and a length of the resource cycle, where the specifiedtime offset is based at least in part on a periodicity of multimediadata bursts, and where the resource cycle number is based at least inpart on the specified time offset; and receive a multimedia data burstduring the subframe. Additionally, or alternatively, the communicationmanager 140 may perform one or more other operations described herein.

In some aspects, a network entity (e.g., base station 110) may include acommunication manager 150. As described in more detail elsewhere herein,the communication manager 150 may prepare for communication with a UEaccording to a DRX cycle; and transmit, starting at a subframe, a databurst based at least in part on a specified time offset that is added toan on duration of the DRX cycle based at least in part on a DRX cyclenumber of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset.

In some aspects, the communication manager 150 may prepare forcommunication with a UE according to a DRX cycle; and transmit, startingat a subframe, a data burst based at least in part on a specified timeoffset that is added to an on duration of the DRX cycle based at leastin part on a DRX cycle number of the DRX cycle and a length of the DRXcycle, where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle number isbased at least in part on the specified time offset.

In some aspects, the communication manager 150 may prepare forcommunication with a UE according to a resource cycle; and transmit,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an instance of the resource cyclebased at least in part on a resource cycle number of the resource cycleand a length of the resource cycle, where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, wherethe resource cycle number is based at least in part on the specifiedtime offset, and where the resource cycle number is based at least inpart on the specified time offset. Additionally, or alternatively, thecommunication manager 150 may perform one or more other operationsdescribed herein.

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of a base station 110 incommunication with a UE 120 in a wireless network 100, in accordancewith the present disclosure. The base station 110 may be equipped with Tantennas 234 a through 234 t, and UE 120 may be equipped with R antennas252 a through 252 r, where in general T≥1 and R≥1.

At the base station 110, a transmit processor 220 may receive data, froma data source 212, intended for the UE 120 (or a set of UEs 120). Thetransmit processor 220 may select one or more modulation and codingschemes (MCSs) for the UE 120 based at least in part on one or morechannel quality indicators (CQIs) received from that UE 120. The basestation 110 may process (e.g., encode and modulate) the data for the UE120 based at least in part on the MCS(s) selected for the UE 120 and mayprovide data symbols for the UE 120. The transmit processor 220 mayprocess system information (e.g., for semi-static resource partitioninginformation (SRPI)) and control information (e.g., CQI requests, grants,and/or upper layer signaling) and provide overhead symbols and controlsymbols. The transmit processor 220 may generate reference symbols forreference signals (e.g., a cell-specific reference signal (CRS) or ademodulation reference signal (DMRS)) and synchronization signals (e.g.,a primary synchronization signal (PSS) or a secondary synchronizationsignal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (e.g., precoding) on thedata symbols, the control symbols, the overhead symbols, and/or thereference symbols, if applicable, and may provide a set of output symbolstreams (e.g., T output symbol streams) to a corresponding set of modems232 (e.g., T modems), shown as modems 232 a through 232 t. For example,each output symbol stream may be provided to a modulator component(shown as MOD) of a modem 232. Each modem 232 may use a respectivemodulator component to process a respective output symbol stream (e.g.,for OFDM) to obtain an output sample stream. Each modem 232 may furtheruse a respective modulator component to process (e.g., convert toanalog, amplify, filter, and/or upconvert) the output sample stream toobtain a downlink signal. The modems 232 a through 232 t may transmit aset of downlink signals (e.g., T downlink signals) via a correspondingset of antennas 234 (e.g., T antennas), shown as antennas 234 a through234 t.

At the UE 120, a set of antennas 252 (shown as antennas 252 a through252 r) may receive the downlink signals from the base station 110 and/orother base stations 110 and may provide a set of received signals (e.g.,R received signals) to a set of modems 254 (e.g., R modems), shown asmodems 254 a through 254 r. For example, each received signal may beprovided to a demodulator component (shown as DEMOD) of a modem 254.Each modem 254 may use a respective demodulator component to condition(e.g., filter, amplify, downconvert, and/or digitize) a received signalto obtain input samples. Each modem 254 may use a demodulator componentto further process the input samples (e.g., for OFDM) to obtain receivedsymbols. A MIMO detector 256 may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable,and may provide detected symbols. A receive processor 258 may process(e.g., demodulate and decode) the detected symbols, may provide decodeddata for the UE 120 to a data sink 260, and may provide decoded controlinformation and system information to a controller/processor 280. Theterm “controller/processor” may refer to one or more controllers, one ormore processors, or a combination thereof. A channel processor maydetermine a reference signal received power (RSRP) parameter, a receivedsignal strength indicator (RSSI) parameter, a reference signal receivedquality (RSRQ) parameter, and/or a CQI parameter, among other examples.In some examples, one or more components of the UE 120 may be includedin a housing 284.

The network controller 130 may include a communication unit 294, acontroller/processor 290, and a memory 292. The network controller 130may include, for example, one or more devices in a core network. Thenetwork controller 130 may communicate with the base station 110 via thecommunication unit 294.

One or more antennas (e.g., antennas 234 a through 234 t and/or antennas252 a through 252 r) may include, or may be included within, one or moreantenna panels, one or more antenna groups, one or more sets of antennaelements, and/or one or more antenna arrays, among other examples. Anantenna panel, an antenna group, a set of antenna elements, and/or anantenna array may include one or more antenna elements (within a singlehousing or multiple housings), a set of coplanar antenna elements, a setof non-coplanar antenna elements, and/or one or more antenna elementscoupled to one or more transmission and/or reception components, such asone or more components of FIG. 2 .

On the uplink, at the UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports that include RSRP, RSSI, RSRQ, and/or CQI) from thecontroller/processor 280. The transmit processor 264 may generatereference symbols for one or more reference signals. The symbols fromthe transmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modems 254 (e.g., for DFT-s-OFDM orCP-OFDM), and transmitted to the base station 110. In some examples, themodem 254 of the UE 120 may include a modulator and a demodulator. Insome examples, the UE 120 includes a transceiver. The transceiver mayinclude any combination of the antenna(s) 252, the modem(s) 254, theMIMO detector 256, the receive processor 258, the transmit processor264, and/or the TX MIMO processor 266. The transceiver may be used by aprocessor (e.g., the controller/processor 280) and the memory 282 toperform aspects of any of the methods described herein (e.g., withreference to FIGS. 3-31 ).

At the base station 110, the uplink signals from UE 120 and/or other UEsmay be received by the antennas 234, processed by the modem 232 (e.g., ademodulator component, shown as DEMOD, of the modem 232), detected by aMIMO detector 236 if applicable, and further processed by a receiveprocessor 238 to obtain decoded data and control information sent by theUE 120. The receive processor 238 may provide the decoded data to a datasink 239 and provide the decoded control information to thecontroller/processor 240. The base station 110 may include acommunication unit 244 and may communicate with the network controller130 via the communication unit 244. The base station 110 may include ascheduler 246 to schedule one or more UEs 120 for downlink and/or uplinkcommunications. In some examples, the modem 232 of the base station 110may include a modulator and a demodulator. In some examples, the basestation 110 includes a transceiver. The transceiver may include anycombination of the antenna(s) 234, the modem(s) 232, the MIMO detector236, the receive processor 238, the transmit processor 220, and/or theTX MIMO processor 230. The transceiver may be used by a processor (e.g.,the controller/processor 240) and the memory 242 to perform aspects ofany of the methods described herein (e.g., with reference to FIGS. 3-31).

The controller/processor 240 of a network entity (e.g., base station110), the controller/processor 280 of the UE 120, and/or any othercomponent(s) of FIG. 2 may perform one or more techniques associatedwith methodologies for DRX, such as setting a hyper frame length forDRX, as described in more detail elsewhere herein. For example, thecontroller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform or direct operations of, for example, process 2000 ofFIG. 20 , process 2100 of FIG. 21 , process 2200 of FIG. 22 , process2300 of FIG. 23 , process 2400 of FIG. 24 , process 2500 of FIG. 25 ,and/or other processes as described herein. The memory 242 and thememory 282 may store data and program codes for the base station 110 andthe UE 120, respectively. In some examples, the memory 242 and/or thememory 282 may include a non-transitory computer-readable medium storingone or more instructions (e.g., code and/or program code) for wirelesscommunication. For example, the one or more instructions, when executed(e.g., directly, or after compiling, converting, and/or interpreting) byone or more processors of the base station 110 and/or the UE 120, maycause the one or more processors, the UE 120, and/or the base station110 to perform or direct operations of, for example, process 2000 ofFIG. 20 , process 2100 of FIG. 21 , process 2200 of FIG. 22 , process2300 of FIG. 23 , process 2400 of FIG. 24 , process 2500 of FIG. 25 ,and/or other processes as described herein. In some examples, executinginstructions may include running the instructions, converting theinstructions, compiling the instructions, and/or interpreting theinstructions, among other examples.

In some aspects, a UE (e.g., a UE 120) includes means for sleeping inassociation with a DRX cycle; means for waking up, starting at asubframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset; and/or means for receiving amultimedia data burst during the subframe. The means for the UE toperform operations described herein may include, for example, one ormore of communication manager 140, antenna 252, modem 254, MIMO detector256, receive processor 258, transmit processor 264, TX MIMO processor266, controller/processor 280, or memory 282.

In some aspects, the UE includes means for sleeping in association witha DRX cycle; means for waking up, starting at a subframe, based at leastin part on a specified time offset that is added to an on duration ofthe DRX cycle based at least in part on a DRX cycle number of the DRXcycle and a DRX time reference system frame number (SFN), where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset; and/or means for receiving amultimedia data burst during the subframe.

In some aspects, the UE includes means for sleeping in association witha resource cycle; means for waking up, starting at a subframe, based atleast in part on a specified time offset that is added to an instance ofthe resource cycle based at least in part on a resource cycle number ofthe resource cycle and a length of the resource cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the resource cycle number is based atleast in part on the specified time offset; and/or means for receiving amultimedia data burst during the subframe.

In some aspects, a network entity (e.g., base station 110) includesmeans for preparing for communication with a UE according to a DRXcycle; and/or means for transmitting, starting at a subframe, a databurst based at least in part on a specified time offset that is added toan on duration of the DRX cycle based at least in part on a DRX cyclenumber of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset. In some aspects, the means for thenetwork entity to perform operations described herein may include, forexample, one or more of communication manager 150, transmit processor220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236,receive processor 238, controller/processor 240, memory 242, orscheduler 246.

In some aspects, the network entity includes means for preparing forcommunication with a UE according to a DRX cycle; and/or means fortransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a length of the DRX cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset.

In some aspects, the network entity includes means for preparing forcommunication with a UE according to a resource cycle; and/or means fortransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an instance of theresource cycle based at least in part on a resource cycle number of theresource cycle and a length of the resource cycle, where the specifiedtime offset is based at least in part on a periodicity of multimediadata bursts, and where the resource cycle number is based at least inpart on the specified time offset, and where the resource cycle numberis based at least in part on the specified time offset.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofcontroller/processor 280.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofthe controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

FIG. 3 is a diagram illustrating an example 300 of devices designed forlow latency applications, in accordance with the present disclosure.

Some devices, including devices for XR, may require low-latency trafficto and from an edge server or a cloud environment. Example 300 showscommunications between an XR device and the edge server or the cloudenvironment, via a base station (e.g., gNB). The XR device may be anaugmented reality (AR) glass device, a virtual reality (VR) glassdevice, or other gaming device. XR devices may have limited batterycapacity while being expected to have a battery life of a smartphone(e.g., full day of use). Battery power is an issue even when the XRdevice is tethered to a smartphone and uses the same smartphone battery.XR device power dissipation may be limited and may lead to anuncomfortable user experience and/or a short battery life.

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3 .

FIG. 4 is a diagram illustrating an example 400 of low-latency trafficand power states, in accordance with the present disclosure.

Power dissipation may be reduced by limiting an amount of time thatprocessing resources of the XR device are active for computations andpower consumption. Some wireless communications systems may a support aUE, such as the XR device, that operates in a DRX mode. A UE in a DRXmode may transition between sleeping and waking up. Sleeping may includeentering or being in a DRX inactive state (e.g., sleep state, powersaving mode) for power conservation. Waking up may include entering aDRX active state (e.g., active time) from a DRX inactive state for datatransmission and reception. The active state for data transmission andreception may be referred to as a DRX “ON-duration.” A DRX cycle may bea time duration that includes a sleep state and an active ON-durationstate for a UE. The DRX cycle may start at the beginning of anON-duration and end at the beginning of the next ON-duration. DifferentDRX cycles may have different lengths (e.g., 8 milliseconds (ms), 16ms). A UE that uses different DRX cycles may have non-uniform cycledurations within a DRX time period, which is a larger time duration thatincludes multiple DRX cycles. Such non-uniform cycle durations mayprovide DRX ON-durations that are aligned with a periodicity of downlinktraffic to the UE. In some cases, the DRX time period may correspond toan anchor cycle that spans a set of DRX cycles, and a subset of the setof DRX cycles may have a different cycle duration than other DRX cyclesof the set of DRX cycles. In some cases, an ON-duration offset value maybe indicated for one or more DRX cycles within the DRX time period(e.g., via downlink control information (DCI) or a MAC CE).

By offloading some computations to an edge server, an XR device may saveprocessing resources. Example 400 shows a scenario where an XR devicemay split computations for an application with the edge server on theother side of a base station. The edge server may render video frames,such as intra-coded (I) frames and predicted (P) frames, encode thevideo frames, align the video frames with user pose information, andperform other related computations. However, this means there may bemore traffic between the XR device and the edge server, which will causethe XR device to consume more power and signaling resources. XR downlinktraffic (e.g., video frames) may have a periodic pattern thatcorresponds to a frame rate of transmitted video data (e.g., H.264/H.265encoded video). Such downlink traffic may be quasi-periodic with a databurst every frame at one frame-per-second (1/fps), or two possiblystaggered “eye-buffers” per frame at 1/(2*fps). For example, XR downlinktraffic may include 100+ kilobytes (KB) of data for 45, 60, 75, or 90frames per second (e.g., every 11 ms, 13 ms, 16 ms, or 22 ms). XR uplinktraffic may include controller information for gaming, information forVR split rendering, and/or the user pose information. The XR uplinktraffic may include 100 bytes every 2 ms (500 Hz). The XR device mayreduce this periodicity to align the XR uplink traffic with the XRdownlink traffic.

For low-latency applications, the DRX cycle and a start offset of a DRXcycle are to be time-aligned to downlink traffic arrivals. For example,the XR device may serve the user and enter a brief sleep state in a DRXcycle and do so between video frames. The XR device and the edge servermay attempt to align the uplink and downlink DRX cycles as part ofconnected DRX (CDRX). However, there are DRX-multimedia timingmismatches that prevent such alignment and that prevent successful useof CDRX. For example, an update rate may be, for example, 120 Hz or 60Hz, thus resulting in a downlink traffic burst arrival periodicity of8.333 ms or 16.667 ms, respectively. However, conventional DRXconfiguration may have one millisecond as the finest granularity for aDRX cycle, and the start of the ON-duration may be aligned tomillisecond time boundaries. These partial millisecond differences maycompound with each instance of a period to misalign the DRX cycle andthe XR traffic periodicity. For example, the XR traffic period may driftto a middle of the DRX cycle. This causes an increase in latency andpower consumption.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 4 .

FIG. 5 illustrates an example 500 of a misalignment of a DRX cycle andXR traffic periodicity, in accordance with the present disclosure.Example 500 shows downlink traffic burst arrivals 505 that may include anumber of downlink traffic bursts 510 that are transmitted according toa periodic pattern. Example 500 also shows a first conventional DRXconfiguration 515 and a second conventional DRX configuration 520.

The downlink traffic bursts 510 may include, for example, XR downlinktraffic with a periodic pattern that corresponds to a frame rate oftransmitted data (e.g., H.264/H.265 encoded video). An update rate maybe, for example, 120 Hz or 60 Hz, thus resulting in a downlink trafficburst arrival periodicity of 8.333 ms or 16.667 ms, respectively.However, the first conventional DRX configuration 515 and the secondconventional DRX configuration 520 may have one millisecond as thefinest granularity for a DRX cycle, and the start of the ON-duration maybe aligned to millisecond time boundaries.

In the example of FIG. 5 , a 120 Hz update rate is illustrated for burstarrivals 505, thus resulting in an 8.333 ms periodicity for the downlinktraffic bursts 510. In the event that the first conventional DRXconfiguration 515 is selected and an initial DRX cycle has anON-duration that is aligned with the first downlink traffic burst 510-a,the second downlink traffic burst 510-b and the third downlink trafficburst 510-a will each also be within the subsequent two ON-durations.However, the fourth downlink burst 510-d would miss the fourthON-duration, as it would occur 0.333 seconds after the end of the fourthON-duration. If the second conventional DRX configuration 520 were to beselected instead, the result would be that the first downlink trafficburst 510-a would be aligned with an ON-duration, but subsequentdownlink traffic bursts 510-b, 510-c, and 510-d would each miss theON-duration.

Further, if the DRX configuration were to be modified to have a finestgranularity corresponding to a slot or symbol, such misalignments maycontinue to occur due to the burst arrivals 505 having a periodicitythat is not a multiple of a slot or symbol duration. For example, as thetraffic burst interval (120 Hz or 60 Hz) expressed in milliseconds has afactor of 3 in the denominator, which cannot divide into the numerator(i.e., 1000/120=X/3, where X is an integer such as 25 for a 120 Hzupdate rate or 50 for 60 Hz update rate). More generally, if DRX cyclegranularity can be defined in slots, the expression would be the numberof slots in a second divided by the source update rate in Hz.Misalignments between the downlink traffic bursts 510 and ON-durationsmay add additional latency to communications, where the additionallatency is cyclic. For example, in a first missed ON-duration of an 8 msDRX configuration, the downlink traffic burst may be retransmitted at anext ON-duration, which occurs 7 ms later than the missed ON-duration.Subsequent downlink traffic bursts will have a lower latency, whichreduces by 0.333 ms each cycle, until the downlink traffic bursts areagain aligned with ON-durations in 21 cycles, with such alignmentlasting for three cycles. Thus, the alignment and misalignment ofdownlink traffic bursts in such an example would be cyclic with a periodof 24 cycles, and an average latency of about 3 ms. In some cases, toreduce the latency, the DRX cycle duration may be reduced, which alsohas a corresponding increase in power consumption due to the extraON-durations. As a result, the XR device may consume additionalprocessing resources.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 5 .

FIG. 6 illustrates an example 600 of an anchor cycle with a leap DRXcycle, in accordance with the present disclosure.

In some scenarios, a UE (e.g., XR device) and the network may use ananchor cycle with a leap DRX cycle to better align the DRX cycle toreduce latency and conserve energy consumption. For example, the UE andthe network may implement an anchor cycle with a leap DRX cycle. Ananchor cycle may include a cycle that includes multiple DRX cycles, oneof which is a DRX leap cycle. A DRX leap cycle may occur every specifiedquantity of DRC cycles. The DRX leap cycle may be a DRX cycle thatadjusts a timing of its ON-duration (e.g., by using an additional DRXoffset that aligns the ON-duration with multimedia periodicity).Downlink traffic burst arrivals 605 may include a number of downlinktraffic bursts 610 that are transmitted according to a periodic pattern.The downlink traffic bursts 610 may include, for example, XR downlinktraffic that has a periodic pattern with a downlink traffic bursts 610every 8.333 ms, for example. An anchor cycle 620 may, for example, spanthree DRX cycles 615, and the third DRX cycle may be a leap cycle 625that has a longer cycle duration than the initial two DRX cycles. Insome cases, the anchor cycle 620, which may be an example of a DRX timeperiod, may span more or fewer DRX cycles, and may include one or moreleap cycles 625. The anchor cycle 620 may be used as a basis fordetermining timing for radio resource management (RRM) functions. Insome cases, the leap cycle 625 may include one or more additional slotsthan other DRX cycles of the anchor cycle 620. The position of the leapcycle(s) 625 can be varied within the anchor cycle 620. While example600 shows burst arrivals 605 associated with periodic traffic having a120 Hz update rate and the anchor cycle 620 includes three DRX cycleswith durations of 8 ms, 8 ms, and 9 ms, other configurations may be usedfor different periodicities or patterns of downlink traffic. Forexample, for periodic traffic with a 60 Hz update rate, an anchor cyclewith three DRX cycles of 16 ms, 17 ms, 17 ms may be configured, or thethree DRX cycles may have durations of 16 ms, 16 ms, 18 ms,respectively. The order of the leap cycle(s) 625 among the DRX cycleswithin the anchor cycle 620 may also be configured. For example, for 120Hz update rate, DRX cycles with duration of (8 ms, 8 ms, 9 ms), (8 ms, 9ms, 8 ms), or (9 ms, 8 ms, 8 ms) can be configured. Support for suchvaried options in the ordering may help with offsetting multiple usersin time for their respective ON-durations, in order to better distributeutilization of resources over time.

In some cases, a base station may configure a UE with a DRXconfiguration via radio resource control (RRC) signaling. For example, abase station may identify that periodic traffic is being transmitted tothe UE (e.g., based on XR application traffic having a certain updaterate, or based on historical downlink burst transmissions to the UE),and that the periodic traffic does not align with slot or subframeboundaries. The base station may determine the anchor cycle duration(e.g., based on a number of periods of the downlink traffic bursts 610that correspond to millisecond time boundaries, such as three 8.333 msperiods that provide a 25 ms anchor cycle duration), a number of DRXcycles within the anchor cycle 620, and which of the DRX cycles are tohave different cycle durations. In some cases, the RRC signaling mayindicate the anchor cycle duration in milliseconds, the number of DRXcycles in the anchor cycle, and the cycle duration of each DRX cycle(e.g., 8, 8, 9). In some cases, the UE may signal to the base stationthat the UE has a capability to perform DRX procedures with non-uniformDRX cycles, and the base station may enable the capability whenproviding the DRX configuration. In other cases, non-uniform DRX cyclesmay be configured using other techniques, such as by adjusting astarting offset of an ON-duration of a DRX cycle, as discussed inconnection with FIG. 7 .

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 6 .

FIG. 7 illustrates an example 700 of a DRX configuration with dynamicoffset adjustment that supports DRX techniques with non-uniform cycledurations, in accordance with the present disclosure. Example 700 showsdownlink traffic burst arrivals 705 that include a number of downlinktraffic bursts 710 that are transmitted according to a periodic pattern.Example 700 also shows a DRX configuration 715 with non-uniform cycledurations.

The downlink traffic bursts 710 may include, for example, XR downlinktraffic that has a periodic pattern with a downlink traffic bursts 710every 8.333 ms. In example 700, DRX configuration 715 has aconfiguration with an 8 ms DRX cycle duration and a 1 ms ON-duration. Inthe initial DRX cycles of the downlink traffic bursts 710, theON-duration may have a zero millisecond offset, such that the firstdownlink traffic burst 710-a, the second downlink traffic burst 710-b,and the third downlink traffic burst 710-c are aligned withON-durations. A UE may make an adjustment 720 to the DRX ON-durationstart offset following the third downlink burst 710-c, which mayincrease the ON-duration start offset by one millisecond in thisexample, such that the adjusted DRX ON-duration is aligned with thefourth downlink traffic burst 710-d. The UE may make another adjustmentto the ON-duration offset back to the original offset following thefourth downlink traffic burst 710-d, and thus the DRX cycles may beconfigured to align ON-durations with downlink traffic bursts 710.

In some cases, the DRX ON-duration start offset adjustment can bepredefined based on a specification, or defined in the DRX configuration(e.g., that is provided in RRC signaling). For example, different typesof traffic (e.g., XR traffic) and different periodicities (e.g., basedon a 120 Hz or 60 Hz update rate) DRX starting offsets may be definedaccording to a pattern such as in example 700 (e.g., every 4th DRX cyclehas a 1 ms starting offset added). In some cases, the DRX startingoffset may be dynamically indicated (e.g. based on MAC CE or DCI) in aprior downlink transmission.

As indicated above, FIG. 7 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 7 .

FIG. 8 is a diagram illustrating an example 800 of using a short cadencevalue for DRX, in accordance with the present disclosure. Example 800shows traffic burst arrivals 810 that are arriving at a rate of 120 Hz.

The techniques described in connection with FIGS. 3-7 may improvealignment of DRX cycles and XR traffic to reduce mismatches betweenburst traffic and DRX ON-duration times. However, according to variousaspects described herein, a UE (e.g., an XR device) and the network mayfurther improve such alignment by using a DRX short cadence thatcorresponds to a number of Hz (e.g., instances per second) rather thanan integer ms value. The DRX short cadence value may correspond to anumber of Hz, for example, by being defined by a number of Hz or bybeing defined by a value that is based on or derived from a number of Hzor a similar or related unit. The DRX short cadence (drx-ShortCadence)may be, for example, 45 Hz, 60 Hz, 90 Hz, or 120 Hz, so as to alignON-duration times of the UE with traffic bursts that are received by theUE according to a video frame rate. That is, the DRX short cadence valuemay be a DRX timing value that corresponds to a same time unit orfrequency unit by which traffic bursts are received by the UE (e.g.,video frame rate). This is in contrast to a regular DRX cycle with a DRXlong cycle that is a length (time duration) of a DRX cycle and that hasa unit granularity of milliseconds. Once the base station (e.g., gNB)obtains the frame rate of traffic bursts to the UE, or the periodicityof the traffic bursts to the UE, the base station may set the DRX shortcadence value. The UE may receive the DRX short cadence value from thebase station or obtain the DRX short cadence value based at least inpart on the frame rate or the periodicity of the traffic.

The UE may use the DRX short cadence value to determine when to wake upfor an ON-duration and decode physical downlink control channel (PDCCH)grants from the base station, as part of DRX short cadence cycles 820.The UE may determine when to wake up subframe by subframe, or slot byslot. For example, as shown by reference number 830, the UE maycalculate, in the first part of a current subframe (having a subframeidentifier n), whether specific criteria are satisfied for the currentsubframe. The criteria may be associated with the DRX short cadencevalue and subframe identifiers and may be designed such that subframes(or slots) that satisfy the condition align with a timing of the framerate or the periodicity of the traffic bursts received by the UE. Eachsubframe may be 1 ms and include multiple slots (e.g., 2, 6, 8). Thecriteria may be associated with a system frame number (SFN). For asubframe with subframe identifier n=[(SFN*10)+subframe number], the UEmay wake up if a first ceiling value (smallest integer higher thancalculated value) of (n*drx−ShortCadence/1000)+1 is equal to a secondceiling value of ((n+1)*(drx−ShortCadence/1000)). The SFN may be anumber between 0 and 1023 of a frame, and the subframe number may be anumber between 0 and 9 within the frame. For example, if the DRX cadencevalue is 120 Hz and the subframe has a subframe number of 5 in a framewith a SFN of 800, a subframe identifier n for the subframe may be(800*10)+5, or 8005. A first ceiling value may be a smallest integer of(8005*120/1000)+1, or 961. A second ceiling value may be a smallestinteger of (8005+1)*(120/1000), or 960. The first ceiling value and thesecond ceiling value are not equal, and thus the UE does not satisfy thecriteria and wake up for this subframe. However, a later subframe with asubframe number of 8, may render a first ceiling value of 961 (smallestinteger of (8008*120/1000)+1) and a second ceiling value of 961(smallest integer of (8008+1)*(120/1000)), and thus the UE may satisfythe criteria and wake up during that subframe. The calculation may beperformed at the start of each subframe. In some aspects, multiplecalculations for multiple subframes may be made at one time.

In other words, the UE may satisfy some type of criteria that isassociated with the DRX short cadence (corresponding to Hz) and asubframe identifier of the subframe that uniquely identifies thesubframe among consecutive subframes within a cycle or time period. Thecriteria, or whatever is calculated for a given subframe, may bedesigned to use the DRX short cadence to wake up for subframes accordingto a frame rate or a periodicity of the traffic bursts received by theUE.

As shown by reference number 835, the UE may wake up for an ON-durationat the current subframe. When the UE wakes up, the UE may start a DRXON-duration timer (drx-onDurationTimer). The DRX ON-duration timer maybe a minimum time duration that the UE is to be awake and may be, forexample, 1 ms or 2 ms. For example, if the UE wakes up at subframe 8,and the DRX ON-duration timer is 2 ms, the UE may stay awake throughsubframes 8 and 9. If there is no more traffic, the UE may go back tosleep. In example 800, the DRX ON-duration timer is 1 ms. The DRXON-duration timer may be started for a DRX group.

In some aspects, there may be a leap of 1 subframe every specifiednumber of cycles, similar to the leap-cycle technique described inconnection with FIG. 6 . For example, for a cycle of 8 ms, there may bea leap of 1 subframe (1 ms) every 3 cycles to accommodate the ⅓ subframepart when the duty cycle is 8.333 ms for 120 Hz. That is, for a DRXshort cadence of 120 Hz, the UE may determine to wake up for subframen=8, 16, 25, 33, 41, 50, and so forth. As shown by reference number 840,after waking up at subframes 8 and 16, instead of subframe 24, the UEmay leap 1 subframe to wake up at subframe 25. If example 800 were tocontinue to show ON-duration subframes, the UE may then wake up 8 mslater at subframe 33, and another 8 ms later at subframe 41. Instead ofwaking up 8 ms later at subframe 49, the UE may leap 1 subframe and wakeup at subframe 50. In some aspects, the UE may skip calculations for oneor more subframes after an ON-duration until the next possibleON-duration approaches.

In some aspects, the UE may use a DRX start offset and/or a DRX slotoffset to provide for more granularity as to when to wake up within asubframe, in order to more closely align with the traffic periodicity ofthe UE. The UE may wake up and start a DRX ON-duration timer after a DRXstart offset (drx-StartOffset) from a beginning of the subframe(n+drx-StartOffset) and/or a DRX slot offset (drx-SlotOffset). The DRXstart offset may be a number of ms or microseconds (s) (or set to zeroms or s for no DRX start offset), symbols, or mini-slots. The DRX startoffset may be used to stagger multiple UEs in time. The DRX slot offsetmay be a number of slots. For example, if there are 8 slots in asubframe (such as for mmWave), each slot is 125 s or 0.125 ms. If theDRX slot offset is 2 slots, the wake up time is shifted (2*0.125) or0.250 ms. If wake up times, according to 120 Hz, were 8 ms, 16 ms, 25ms, 33 ms, 41 ms, 50 ms, and so forth, the UE may use the DRX slotoffset to better match the traffic bursts at 8.33 ms, 16.66 ms, and 25ms by using a DRX slot offset of 2 slots at subframe 8 for 8.250 ms, aDRX slot offset of 5 slots at subframe 16 for 16.625 ms, no DRX slotoffset at subframe 25 for 25.000 ms, and so forth, such as shown by thetable for 120 Hz in FIG. 8 . As a result, the UE may better align theDRX cycle and the traffic period to further reduce latency and conservesignaling resources.

As indicated above, FIG. 8 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 8 .

FIG. 9 is a diagram illustrating an example 900 of using a short cadencevalue for DRX for slot positions, in accordance with the presentdisclosure. Example 900 shows a traffic burst 905 among multiple burstarrivals 910 that arrive at a rate of 120 Hz. The burst arrivals 910 inexample 900 may be the same as the burst arrivals 810 shown in example800 of FIG. 8 , except that the timeline in example 900 is magnified inorder to show multiple slots for a subframe.

In some aspects, the calculations per subframe that are based on asubframe identifier may be extended to slot positions, with a slotidentifier k. That is, the criteria for waking up may be based at leastin part on slot identifier k being equal to (((SFN*10)+subframenumber)*slots per second)+a slot number. The UE may wake up and start aDRX ON-duration timer at slot k if a first ceiling value of(k*drx-ShortCadence/1000*slots per second)+1 is equal to a secondceiling value of ((k+1)*(drx-ShortCadence/1000*slots per second)). Thecalculations may be per slot rather than per subframe. As shown byreference number 920, the UE may determine if a calculation for acurrent slot, based at least in part on the DRX short cadence and theslot identifier, satisfies the criteria for waking up. As shown byreference number 925, if the UE is to wake up, the UE may wake up forthe ON-duration 930, which may be a subframe or 8 slots. In someaspects, the calculation may be performed all at once at a beginning ofa subframe. In other words, the UE may satisfy some criteria that isassociated with the DRX short cadence value (corresponding to Hz) and aslot identifier of the slot that uniquely identifies the slot amongconsecutive slots within a cycle or time period. The criteria, orwhatever is calculated for a given slot, may be designed to use the DRXshort cadence value to wake up for slots according to a frame rate or aperiodicity of the traffic bursts to the UE. In some aspects, the UE mayskip calculations for one or more slots or subframes after theON-duration.

In some aspects, the UE may wake up and start a DRX ON-duration timerafter a DRX start slot offset (drx-StartSlotOffset) from a beginning ofthe subframe (n+drx-StartOffset). The DRX start slot offset may be anumber of ms, microseconds (s) (or set to zero ms or s for no DRX startoffset), symbols, slots, or mini-slots. The DRX start slot offset may beused to stagger the UE and the other UEs in time. The DRX start slotoffset may be updated based at least in part on how many UEs aretransmitting, how long the UEs are staying, and if there are changes toUE behavior.

As indicated above, FIG. 9 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 9 .

FIG. 10 is a diagram illustrating an example 1000 of using a shortcadence value for DRX, in accordance with the present disclosure. Asshown in FIG. 10 , a base station 1010 (e.g., base station 110) maycommunicate with a UE 1020 (e.g., UE 120). The base station 1010 and theUE 1020 may be part of a wireless network (e.g., wireless network 100).

The UE 1020 may obtain a DRX short cadence value, which may be definedas a number of Hz. As shown by reference number 1025, the base station1010 may transmit the DRX short cadence value to the UE 120. The UE 1020may also obtain the DRX short cadence value from stored configurationinformation. For example, the UE 1020 may select a DRX short cadencevalue from among multiple DRX short cadence values based at least inpart on a determined periodicity of traffic bursts (e.g., video framerate) transmitted by the base station 1010, as shown by reference number1030.

As shown by reference number 1035, the UE 1020 may sleep and wake upaccording to the DRX short cadence value. For example, the UE 1020 maycalculate, for each subframe, whether a subframe identifier causes theUE 1020 meet the criteria for waking up, based at least in part on theDRX short cadence value. The DRX short cadence value (drx-ShortCadence)may be, for example, 120 Hz, and subframe identifiern=[(SFN*10)+subframe number]. If the subframe identifier n=7,ceil(n*drx-ShortCadence/1000)+1=2 andceil((n+1)*drx-ShortCadence/1000)=1. As 2 does not equal 1, the criteriaare not satisfied (condition is false). If the subframe identifier n=8,ceil(n*drx-ShortCadence/1000)+1=2 andceil((n+1)*drx-ShortCadence/1000)=2. As 2 equals 2, the criteria aresatisfied (condition is true). If the subframe identifier n=9,ceil(n*drx-ShortCadence/1000)+1=3 andceil((n+1)*drx-ShortCadence/1000)=2. As 3 does not equal 2, the criteriaare not satisfied (condition is false). In some aspects, the UE 1020 mayuse a leap cycle, a slot offset, a timing offset, or any other techniquedescribed herein to better match the periodicity of the traffic bursts.The UE 1020 may start an ON-duration timer as part of waking up.

In some aspects, the UE 1020 may perform the calculation for each slot,to determine whether a slot identifier causes the UE 1020 meet thecriteria for waking up, based at least in part on the DRX short cadencevalue. The DRX short cadence value (drx-ShortCadence) may be, forexample, 120 Hz, and slot identifier k=[((SFN*10+subframe number)*slotsper second)+slot number]. The slots per second (slotPerSec) for 120 Hzmay be 8 slots per second. If the slot identifier k=8*8+1,ceil(k*drx-ShortCadence/(1000*slotPerSec))+1=2 andceil((k+1)*drx-ShortCadence/(1000*slotPerSec))=1. As 2 does not equal 1,the criteria are not satisfied (condition is false). If the slotidentifier k=8*8+2, ceil(k*drx-ShortCadence/(1000*slotPerSec))+1=2 andceil((k+1)*drx-ShortCadence/(1000*slotPerSec))=2. As 2 equals 2, thecriteria are satisfied (condition is true). If the slot identifierk=8*8+3, ceil(k*drx-ShortCadence/(1000*slotPerSec))+1=3 andceil((k+1)*drx-ShortCadence/(1000*slotPerSec))=2. As 3 does not equal 2,the criteria are not satisfied (condition is false). In some aspects,the UE 1020 may use a leap cycle, a slot offset, a timing offset, or anyother technique described herein to better match the periodicity of thetraffic bursts.

As indicated above, FIG. 10 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 10

FIG. 11 is a diagram illustrating an example 1100 of using differentshort cadence values, in accordance with the present disclosure. FIG. 11shows tables for different DRX short cadence values, including for 48Hz, 60 Hz, 80 Hz, and 90 Hz to match corresponding frame rates of 48 Hz,60 Hz, 80 Hz, and 90 Hz. Similar to the table for 120 Hz in FIG. 8 , thefirst column in each table of FIG. 11 indicates the periodicity oftraffic bursts (ms between traffic bursts—corresponding to a framerate/short cadence value). The second column in each table indicates thewake up time (in ms) when the criteria is satisfied for the shortcadence value, so as to match the periodicity in the first column. Thethird column indicates (in ms) the wake up time when using a slot offset(e.g., increments of 0.125 ms) in order to more closely match theperiodicity indicated in the first column.

In other words, the UE may calculate, based at least in part on asubframe identifier for a subframe (or a slot identifier for a slot) anda DRX short cadence value of 48 Hz, 60 Hz, 80 Hz, 90 Hz, or 120 Hz,whether the subframe (or the slot) satisfies a criteria for waking up.The criteria may be designed such that the UE wakes up starting at asubframe and/or a slot that is a closest match or alignment for atraffic burst according to the periodicity of the traffic bursts. The UEmay use a slot offset to closely match the periodicity. In this way, theUE more closely matches wake up times with traffic bursts so as toconserve power and processing resources while not missing any trafficbursts during an ON-duration time. The UE may adjust the ON-durationtime as necessary in coordination with the short cadence value and/orthe slot offset value. Note that other DRX short cadence values may beused to match frame rates of 45 Hz, 75 Hz, or other frame rates used forapplications or services that are not explicitly listed herein.

As indicated above, FIG. 11 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 11 .

FIG. 12 is a diagram illustrating an example 1200 of using a shortcadence value for DRX, in accordance with the present disclosure.Example 1200 shows traffic burst arrivals that are arriving at a rate of120 Hz.

There are additional solutions for better matching of a multimediacadence as part of an enhanced connected mode DRX (EC-DRX or eCDRX). Inone scenario, a base station may detect that an offset betweenON-duration occasions needs to be changed, in order to better match thearrival time of the next data burst. In some aspects, the base stationmay transmit a MAC CE to a UE in order to signal a change of an offsetbetween ON-duration occasions. For example, the MAC CE may indicate thatthe next offset is to be increased by 1 ms, or to shift from 8 ms to 9ms. The MAC CE may indicate an offset value from a list of absolutevalues or a quantity of slots to shift an offset (from a relative valuelist).

As indicated above, FIG. 12 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 12 .

FIG. 13 is a diagram illustrating an example 1300 of using a shortcadence value for DRX, in accordance with the present disclosure.Example 1300 shows traffic burst arrivals that are arriving at a rate of120 Hz.

DRX may involve a DRX short cycle. If the DRX short cycle is used for aDRX group, where [(SFN×10)+subframe number] modulo(drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle), the UE maystart drx-onDurationTimer for this DRX group after drx-SlotOffset fromthe beginning of the subframe. [(SFN×10)+subframe number] may define thesubframe index for a DRX cycle. The parameter drx-ShortCycle may definethe subframe periodicity of an ON-duration cycle, and the parameterdrx-StartOffset may define the subframe offset of an ON-duration cycle.

DRX may involve a DRX long cycle. If the DRX long cycle is used for aDRX group, where [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, the UE may start drx-onDurationTimerfor this DRX group after drx-SlotOffset from the beginning of thesubframe.

In some aspects, a two-level DRX configuration may define an outer DRXcycle and an inner DRX cycle to structure a leap DRX cycle. The outerDRX may be the same as legacy DRX, which supports only uniform DRX. Theinner DRX may support sub-cycles that can be non-uniform. The start ofthe first inner DRX cycle may be aligned to the start of the outer DRX,and the end of the last inner DRX cycle may be aligned to the end of theouter DRX. The ON-duration, an inactivity timer, and other DRXparameters for configuration for the inner DRX cycles can be the same asthat of the outer DRX cycle. If the outer DRX cycle is configured to be25 ms as an “anchor-cycle” that depends on the DRX subframe index of[(SFN×10)+subframe number], the inner DRX cycles may be configured to be(8, 8, 9) ms for a set of sub-cycles for ON-duration.

In some aspects, the start of the ON-duration may be defined withrespect to the short DRX cycle and the long DRX cycle. The short DRXcycle may be defined as [(SFN×10)+subframe number] modulo(drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle). The long DRXcycle may be defined as [(SFN×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset.

As indicated above, FIG. 13 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 13 .

FIG. 14 is a diagram illustrating an example 1400 of an SFN wraparound,in accordance with the present disclosure. Example 1400 shows multimediadata burst arrivals that are arriving at a rate of 120 Hz. In example1400, drx-StartOffset is set to 0.

A UE may configure a DRX cycle for a cadence of data bursts, such asevery 8.33 ms at 120 Hz, but the cadence of the data bursts may beassociated with a periodicity of 1000 ms. With a multimedia periodicityof 1000 ms and a DRX cycle of 10,240 ms (1024 SFNs per hyper frame at 10ms each), the hyper frame of the DRX may be misaligned with a frame of amultimedia server every 10.24 seconds. There is a drift 1404 of 1.666 ms(2 ms in example 1400) every 10.24 sec (10,240 ms) due to themisalignment between the hyper frame periodicity (10,240 ms) and themultimedia periodicity. In other words, the hyper frame periodicity(10,240 ms) cannot be divided by the multimedia periodicity (Hz, fps).In an example of 120 Hz XR traffic, 10,240 ms/(1000/120) ms=1228.8frames. The fractional part of 0.8 (or 1−0.8=0.2) is the remainingpartial frame at the end of the hyper frame, and this partial framecauses an SFN wraparound problem in the next hyper frame. Othermultimedia periodicities result in other quantities of frames that donot align with a quantity of SFNs per hyper frame: 45 Hz (460.8 SFNs),48 Hz (491.52 SFNs), 60 Hz (614.4 SFNs), or 90 Hz (921.6 SFNs.

Example 1400 shows an end of the hyper frame (at SFN 1023) and abeginning of the next hyper frame (at SFN 0), or when the SFN numberswrap around (restart or return to 0) for the next hyper frame. When theend of the hyper frame 1402 is reached, an ON-duration wake-up conditionor formula, such as (SFN*10)+subframe number=0, may select a subframefor an ON-duration that is between data bursts due to the SFNwraparound. Because the subframe may not be aligned with a data burst,the data burst may not be received. This may cause a degradation ofcommunications that could consume additional processing resources andsignaling resources.

As indicated above, FIG. 14 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 14 .

FIG. 15 is a diagram illustrating an example 1500 of setting a hyperframe length, in accordance with the present disclosure. Example 1500shows multimedia data burst arrivals that are arriving at a rate of 120Hz.

In some aspects, a network entity (e.g., base station 110) may configurea UE (e.g., UE 120) to set a hyper frame length that is based at leastin part on the cadence of the multimedia data bursts, as shown byreference number 1505. The cadence of the multimedia data bursts maycorrespond to a number of Hz, and a number of frames forming the hyperframe length may be a multiple of a time periodicity of the number ofHz. For example, the UE may set the hyper frame length to be 1000 SFNsrather than 1024 SFNs, such that there is no SFN wraparound at the endof a hyper frame that would misalign ON-duration occasions that arecalculated in the next hyper frame. The hyper frame length may also be1000 frames or 10000 subframes. In some aspects, the UE may maintain anSFN counter for a hyper frame and reset the counter for a next hyperframe upon reaching the hyper frame length (end of the hyper frame). TheUE may initialize the SFN counter with a current SFN. The SFN counterincreases when the SFN is updated. As a result of setting a hyper framelength to match a cadence or periodicity of the multimedia data bursts,there will not be a misalignment and frequent drift of the timing whenthe UE receives the multimedia data bursts, as shown by reference number1510. By adjusting a hyper frame length, the UE may align ON-durationoccasions with data bursts to improve communications and cause the UE toavoid consuming additional processing resources and signaling resources.In some aspects, the network entity may select the hyper frame lengthand transmit the hyper frame length in configuration information.

The UE may use the set hyper frame length by performing a modulooperation with the hyper frame length to determine subframe identifiersof DRX ON-duration subframes for receiving the multimedia data bursts,and the DRX cycle may be configured for a cadence of the multimedia databursts. For example, if a subframe identifier n for calculating anON-duration subframe was previously determined, withn=[(SFN×10)+subframenumber], the UE may now determine the subframe identifier n withn=[(SFN_M×10)+subframe number], where SFN_M is the SFN after a modulooperation with the set hyper frame length (in SFNs). For example, for agiven subframe in sequence N=50000, subframe identifier n for anON-duration wake-up condition or formula would be 50000 mod 10240, or9040, with a hyper frame length of 1024 frames (SFN_M=1024). Bycontrast, for a given subframe N=50000, n would be 50000 mod 10000, or0, with a hyper frame length of 1000 frames (SFN_M=1000), for theON-duration formula.

In some aspects, the ON-duration formula for waking up from anON-duration sleep cycle may include waking up, starting at a subframe,based at least in part on a subframe identifier of the subframe and aDRX cycle periodicity that corresponds a multiple of a multimediaperiodicity (inverse of multimedia cadence in a number of Hz). Forexample, a formula may be [(SFN×numberOfSubframesPerFrame)+subframenumber in theframe]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+floor(N×1000/drx-ShortCadence)]modulo (1024×numberOfSubframesPerFrame). N may be a value that is usedfor sequentially searching for DRX cycle ON-durations. N increments byone for each ON-duration occasion. There is no SFN wraparound withsequential searching value N. The parameter drx-timeReferenceSFN mayprovide an SFN that may be used to offset a resource or start a hyperframe. The UE may use the closest SFN with the indicated numberpreceding the reception of the eCDRX configuration. In some aspects, theceiling of (N×1000/drx-ShortCadence) may be used instead of the floor.(drx-SlotOffset/32×numberOfSlotsPerSubframe) may indicate the slotoffset value in slots when drx-SlotOffset is the value in 1/32 ms, andthe ceiling operation may be used instead of the floor. The termsdrx-ShortCadence and drx-ShortCycle may have a relationship such asdrx-ShortCycle (ms)=1000/drx-ShortCadence (fps).

In some aspects, the formula may be[(SFN×numberOfSubframesPerFrame)+subframe number in theframe]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset(i)+N×drx-ShortCycle]modulo (1024×numberOfSubframesPerFrame).

There may be multiple DRX offsets. The index i may be used to indicateone of the multiple DRX start offsets (drx-StartOffset(i)) and/ormultiple DRX slot offsets (drx-StartOffset(i)). Index i may be aninteger in an RRC information element (e.g., 0 to 10239 fordrx-StartOffset(i), 0 to 31 for drx-SlotOffset(i)). The drx-SlotOffsetmay have a value of, for example, 1/32 ms for 480 kilohertz (KHz)subcarrier spacing (SCS). In one example, three DRX start offsets may bedefined within drx-ShortCycle, i=[0, 1, 2], and drx-StartOffset may bedefined for each i. In this example, with a multimedia cadence of 120Hz, drx-ShortCycle=25, drx-StartOffset(0)=0, drx-StartOffset(1)=8, anddrx-StartOffset(2)=16. Also, drx-SlotOffset(0)=0, drx-SlotOffset(1)=0,drx-SlotOffset(2)=0. Any of the three values of drx-StartOffset(i) anddrx-SlotOffset(i) will activate the drx-onDurationTimer.

There may be multiple DRX start offsets (e.g., unit: subframe, 1 ms)within the drx-ShortCycle. For any i, the drx-onDurationTimer for a DRXgroup may start after drx-SlotOffset(i) from the beginning of thesubframe. The set of multiple drx-StartOffsets and drx-SlotOffsets maybe configured within drx-ShortCycle, and drx-ShortCycle may be set withany integer numbers.

In some aspects, drx-timeReferenceSFN may be an enumerated value, suchas SFN 512, that indicates the SFN used for determination of the offsetof a time domain resource. The UE may use the closest SFN with theindicated number preceding the reception of the eCDRX configuration. IftimeReferenceSFN is not present, timeReferenceSFN may be 0.

In some aspects, at a slot level, an ON-duration formula may be[(SFN×numberOfSlotsPerFrame)+slot number in theframe]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset×numberOfSlotsPerSubframe+floor(drx-SlotOffset/32×numberOfSlotsPerSubframe)+floor(N×numberOfSlotsPerSubframe×1000/drx-ShortCadence)]modulo (1024×numberOfSlotsPerFrame). drx-SlotOffset may be the value in1/32 ms. In some aspects, the ceiling of(N×numberOfSlotsPerSubframe×1000/drx-ShortCadence) may be used insteadof the floor.

In some aspects, the formula may be [(SFN×numberOfSlotsPerFrame)+slotnumber in theframe]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset(i)×numberOfSlotsPerSubframe+floor(drx-SlotOffset(i)/32×numberOfSlotsPerSubframe)+N×drx-ShortCycle]modulo (1024×numberOfSlotsPerFrame). For any i, drx-onDurationTimer maystart for a DRX group at the beginning of the slot. DRX timers (e.g.,drx-InactivityTimer, drx-HARQ-RTT-Timer) may be set with the granularityof the slot. In an example with a multimedia cadence of 120 Hz (30 kHzSCS (0.5 ms), drx-ShortCycle=25×2 slots, drx-StartOffset(0)=0,drx-StartOffset(1)=8, and drx-StartOffset(2)=16.

In some aspects, the formula may be [(SFN×numberOfSlotsPerFrame)+slotnumber in theframe]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset(i)+N×drx-ShortCycle]modulo (1024×numberOfSlotsPerFrame). drx-StartOffset may be set with thegranularity of a slot. The value of drx-StartOffset(i) may be an integerbetween 0 and 327647, for example. The unit for the multiple DRX startoffsets with the drx-ShortCycle may be a slot, and drx-SlotOffset may bemerged into drx-StartOffset. In an example with a multimedia cadence of120 Hz (30 kHz SCS (0.5 ms), drx-ShortCycle=25×2 slots,drx-StartOffset(0)=0 slots, drx-StartOffset(1)=8×2 slots, anddrx-StartOffset(2)=16×2 slots.

In some aspects, a sequential search DRX cycle formula may involve arational number for drx-ShortCycle. The formula may be[(SFN×numberOfSubframesPerFrame)+subframe number in theframe]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+floor(N×drx-ShortCycle)]modulo (1024×numberOfSsubframesPerFrame). In some aspects, a ceiling of(N×drx-ShortCycle)] may be used.

In some aspects, the drx-ShortCycle may be indicated in an RRCinformation element (IE) and may be an enumerated value such asms8and1Over3, ms11and1Over9, ms12and1Over2, ms16and2Over3,ms20and5Over6, ms22and2Over9, ms33and1Over3, or ms41and2Over3. Theserepresent rational numbers associated with DRX cycle periodicity. Arational number may represent a non-integer value for drx-ShortCycle andthus ms8and1Over3 is associated with 120 fps XR traffic. In this examplewith a multimedia cadence (drx-ShortCadence) of 120 fps or 120 Hz,drx-ShortCycle=ms8and1Over3 and drx-StartOffset=0. That is, withdrx-ShortCycle (ms)=1000/drx-ShortCadence (fps) anddrx-ShortCadence=120, drx-ShortCycle=1000/120=25/3=8+⅓ (ms8and1Over3).In another example where drx-ShortCadence=60 fps or 60 Hz,drx-ShortCycle=1000/60=50/3 (16and2Over3).

The network entity may configure the UE with the hyper frame length,such as with an additional information element in an RRC message (e.g.,drx-initialSFN). The network entity may transmit an RRC message with aDRX short cadence value (e.g., drx-ShortCadence) that is an integerbetween 1 and 1000, for example. The network entity may transmit an RRCmessage with a DRX SFN modulo (e.g., drx-SFNModulo) value that is lessthan 1024 SFNs, such as between 1 and 1023. The network entity maytransmit an RRC message indicating an initial value of SFN_M (e.g.,drx-initialSFN), which may be between 0 and 1023 SFNs. The networkentity may transmit a MAC CE indicating an initialization value ortiming of SFN_M, or any other such values.

This new SFN_M value, or otherwise setting the hyper frame length basedat least in part on the cadence of the multimedia data bursts, may beused with other solutions for aligning ON-duration occasions withmultimedia data bursts, as described in connection with FIGS. 6-13 . Forexample, the UE may set a new hyper frame length (and use SFN modulo thenew hyper frame length, or n=[(SFN_M×10)+subframe number]) incalculations for outer DRX cycles in two-level DRX configuration andcalculations for a short DRX cycle and a long DRX cycle. In someaspects, a MAC entity may consider that a sequential N^(th) ON-durationcycle occurs in a subframe for which[(SFN×numberOfSubframesPerFrame)+subframe number in theframe]=[timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+drx-PeriodicOffset(N)]modulo (1024×numberOfSubframesPerFrame). The drx-PeriodicOffset(0)=0when N=0, and thedrx-PeriodicOffset(N)=drx-PeriodicOffset(N−1)+drx-ShortCycleList{(N−1)modulo SIZE(drx-ShortCycleList)}, when N>0. The UE may startdrx-onDurationTimer for this DRX group after drx-SlotOffsetList{(N−1)modulo SIZE(drx-SlotOffset)} from the beginning of the subframe. Thedrx-timeReferenceSFN may provide the SFN used for determination of theoffset of a resource in a time domain. The UE may use the closest SFNwith the indicated number preceding the reception of the DRXconfiguration. The drx-ShortCycleList may be or may be associated with aset of non-uniform DRX short cycles (values in 1 ms, e.g.drx-ShortCycleList=(8,8,9) for 120 Hz). The drx-SlotOffsetList may be ormay be associated with a set of DRX slot offsets. The drx-ShortCycleListmay be a sequence with a size of 1 to maxNrofShortCycle (maximum numberof short cycles) of drx-ShortCycle-r18. The drx-ShortCycle-r18 may be avalue in 1 ms (subframe) between 1 and 640. The drx-StartOffset may bevalue in 1 ms (subframe) between 0 and 10239. This may come fromdrx-LongCycleStartOffset (cf. 1024 (SFN)×10 (Subframes)=10240). Adrx-SlotOffset may be a value in 1/32 ms (480 kHz SCS) between 1 and 31.The drx-timeReferenceSFN may be an enumerated value, such as SFN 512. IftimeReferenceSFN is not present, timeReferenceSFN is 0.

In some aspects, a MAC entity may consider that a sequential N^(th)ON-duration cycle occurs in a slot for which[(SFN×numberOfSlotsPerFrame)+slot number in theframe]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset×numberOfSlotsPerSubframe+floor(drx-SlotOffset/32×numberOfSlotsPerSubframe)+drx-PeriodicOffset(N)]modulo (1024×numberOfSlotsPerFrame). The drx-PeriodicOffset(0)=0 whenN=0, and drx-PeriodicOffset(N)=drx-ShortCycleList{(N−1) moduloSIZE(drx-ShortCycleList)}+drx-PeriodicOffset(N−1) when N>0. Thedrx-ShortCycleList may be a set of non-uniform DRX short cycles (valuesin slots). The drx-ShortCycle-r18 may be a value in slots between 1 and20479. The UE may start the drx-onDurationTimer for this DRX group fromthe beginning of the slot.

In some aspects, the network entity may transmit DCI or a MAC CE commandthat compensates for a subframe index misalignment shift (DRX cycledrift) due to an SFN wraparound. The network entity may indicate a valueto shift a timing of the DRX cycle based at least in part on anindicated shift, such as a 240 subframe (240 ms) shift, a 10,240subframe (10,240 ms) shift, or a specific timing drift (2 ms in Example1400). The value may be a value in a new value set in a shift table listthat can compensate for the subframe index misalignment shift caused bySFN wraparound. The value may be a 1-bit value in DCI or a MAC CEcommand that indicates the SFN wraparound. This value may be transmittedwith a shift value index that references the shift table list or anothershift table list. The UE may apply the shift before a first ON-durationoccasion of the next hyper frame. The UE may use, as a formula for asubframe, [(SFN×numberOfSubframesPerFrame)+subframe number in theframe]=(timeReferenceSFN×numberOfSubframesPerFrame+drx-StartOffset+N×drx-ShortCycle)modulo (1024×numberOfSubframesPerFrame). The UE may start adrx-onDurationTimer for this DRX group after a drx-SlotOffset from thebeginning of the subframe. The UE may use, as a formula for a slot,[(SFN×numberOfSlotsPerFrame)+slot number in theframe]=[timeReferenceSFN×numberOfSlotsPerFrame+drx-StartOffset×numberOfSlotsPerSubframe+floor(drx-SlotOffset/32×numberOfSlotsPerSubframe)+N×drx-ShortCycle×numberOfSlotsPerSubframe]modulo (1024×numberOfSlotsPerFrame). The UE may start adrx-onDurationTimer for this DRX group after a drx-SlotOffset from thebeginning of the slot.

In some aspects, the MAC CE may not be transmitted due to apredictability of an SFN wraparound. In such a case, the network entityand the UE may both expect a 240 ms or a 10,240 ms relative shiftwhenever a hyper frame changes during a DRX cycle. As a result, the UEmay apply the shift before a first ON-duration occasion of the nexthyper frame without receiving a MAC CE indicating the shift. Thisimplicit method may be triggered by a hyper frame change.

In some aspects, the UE may compensate for a timing drift between DRXon-durations and multimedia burst traffic that is associated with amisalignment between a hyper frame length and a periodicity of themultimedia data bursts. For example, the SFN wraparound problem may beresolved by compensating for the drift of 240 ms in the DRX formula. 240subframes can be added every hyper frame in the subframe index,[(SFN×10)+subframe number+M×240] modulo(drx-ShortCycle)=(drx-StartOffset) modulo (drx-ShortCycle). M may startfrom 0 when the DRX is initially configured, and M may increase by 1every hyper frame with a time reference SFN or when SFN returns to 0. Toresolve the timing ambiguity of a DRX configuration message,drx-timeReferenceSFN (0 or 512) can be further considered as the initialreference SFN value.

In some aspects, the SFN wraparound problem may be resolved byaccumulating 10,240 ms in the DRX formula. For example, 10,240 subframescan be added every hyper frame in the subframe index, [(SFN×10)+subframenumber+M×10240] modulo (drx-ShortCycle)=(drx-StartOffset) modulo(drx-ShortCycle). M may start from 0 when the DRX is initiallyconfigured, and M may increase by 1 every hyper frame with a timereference SFN or when SFN returns to 0. To resolve the timing ambiguityof a DRX configuration message, drx-timeReferenceSFN (0 or 512) can befurther considered as the initial reference SFN value. These areexamples and other formulas may add a specified amount of time (e.g.,specified quantity of milliseconds) every hyper frame that satisfies aspecified formula involving subframe numbers and a DRX short cycle.

As indicated above, FIG. 15 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 15 .

FIG. 16 is a diagram illustrating an example 1600 of an RRCconfiguration for DRX cycles, in accordance with the present disclosure.

A UE may receive, from a network entity during a hyper frame, an RRCconfiguration 1602 that indicates DRX cycle information for the hyperframe, including a new timing of ON-duration occasions. However, if theRRC configuration is received late and toward an end of the hyper frame,the DRX configuration may be applied to the next hyper frame rather thanthe current hyper frame. As a result, the UE and the network entity areno longer using the same DRX configuration for the hyper frame and/orfor the next hyper frame.

As indicated above, FIG. 16 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 16 .

FIG. 17 is a diagram illustrating an example 1700 of aligning DRX cyclesand a multimedia periodicity, in accordance with the present disclosure.

Example 1700 shows multiple DRX cycles (DRX cycle 1702, DRX cycle 1704,DRX cycle 1706, among other DRX cycles) configured for a UE (e.g., a UE120). DRX cycle 1706 may be a DRX leap cycle based at least in part onits DRX number (e.g., DRX number 103). DRX cycle 1706 may have a DRXcycle length 1708 (e.g., 32 ms). Meanwhile, data bursts may arriveaccording to a multimedia cadence that is based on, for example, 120 Hz.There is naturally a misalignment due to the mismatch between the Hzgranularity of the multimedia data bursts and the millisecondgranularity of the DRX cycles. Without proper correction, themisalignment will cause the UE to wake up when a data burst is not sentand sleep when a data burst is sent. As a result, data bursts will belost and communication performance will degrade.

As shown by reference number 1710, the UE may sleep in association witha DRX cycle, which may be upcoming DRX cycle 1706. For example, the UEmay sleep in sleep state 1712 of DRX cycle 1704 in anticipation ofupcoming DRX cycle 1706, which will start at the beginning of onduration 1714. To correct the misalignment in advance of waking up, theUE may add a specified time offset 1716 to the on duration 1714. Therewill be a subframe 1718 at this new time location for the on duration1714. As shown by reference number 1720, the UE may wake up at thesubframe 1718. Waking up at the subframe may include waking up fromsleep in time to receive during the subframe. As shown by referencenumber 1725, the UE may receive a multimedia data burst at the subframe1718. The subframe 1718 may have a subframe number 1722 within a frameof the subframe 1718. In some aspects, a starting offset (DRX startingoffset) may be added to the on duration 1714 as well.

According to various aspects described herein, the UE may use a wake-upcondition to determine when to wake up, which may include applying thespecified time offset 1716. The wake-up condition may be based at leastin part on the subframe number 1722 (e.g., subframe 5 of 10 subframes ina frame) of the subframe 1718, which is a subframe of a frame identifiedby an SFN 1736. For example, the UE may wake up based at least in parton the specified time offset 1716 being added to the on duration 1714.The specified time offset 1716 may be added based at least in part onthe DRX cycle number (e.g., 3) and the DRX cycle length 1708 of DRXcycle 1706. The DRX cycle number may be the number of a DRX cycle with alarger time period, such as an anchor cycle. The specified time offset1716 may be a fixed time shift (e.g., 4 ms) for the on duration 1714 andthe start of an on duration timer. The DRX cycle length 1708 may bereferred to as a “DRX long cycle.” The specified time offset 1716 may bebased at least in part on a periodicity 1726 of the multimedia bursts.For example, the UE may wake up when [(SFN×10)+subframe number 1722]modulo the DRX cycle length 1708 is equal to the starting offset1728+(n×specified time offset 1716) modulo the DRX cycle length 1708.The count n may be a count of anchor cycles or a count of when a DRXleap cycle occurs, in which the specified time offset 1716 is applied.The count n may be updated or incremented to n+1 whenever the currentDRX cycle number modulo a specified DRX cycle number 1724 is equal to 0.The specified DRX cycle number 1724 may be a period of DRX leap cyclesor a quantity of DRX cycles at which the specified time offset 1716 isapplied again. For example, if the DRX cycle number for DRX cycle 1706is 3 and the specified DRX cycle number 1724 is 3, the UE may incrementcount n. If the DRX cycle number is currently 4, the UE may notincrement count n. The specified DRX cycle number 1724 may be[(SFN×10)+subframe number 1722]/the DRX cycle length 1708.

Some modifications to this wake-up condition may not successfullyaddress the misalignment of the multimedia data bursts and the DRXcycles. For example, if (n×specified time offset 1716)] is added to aleft side of the modulo such that the wake-up condition is[(SFN×10)+subframe number 1722+(n×specified time offset 1716)] modulothe DRX cycle length 1708 is equal to the starting offset1728+(n×specified time offset) modulo the DRX cycle length 1708, thedifference between the DRX cycle on durations and the periodicity 1726of the multimedia data bursts will continue to increase for eachapplication of the specified time offset 1716. Because of the additional(n×specified time offset 1716) on the left side of the modulo, at alater DRX cycle (e.g., 768 ms), the difference may be equal to the DRXcycle length 1708, which will result in a time duration that is equal tothe specified DRX cycle number 1724 that is used for the modulooperation (modulo result will be 0). This introduces a false DRX cycle.Instead of the difference being set to 0 ms, the difference is now 32 msand increasing.

The wake-up condition may be unsuccessful if the quantity or count ofthe DRX leap cycles is not accounted for. Therefore, in some aspects,the DRX cycle number of a current DRX cycle that is used for updating nmay be based at least in part on the specified time offset 1716. Forexample, the UE may determine the DRX cycle number of a current DRXcycle for updating n by [(SFN×10)+subframe number 1722+(n×specified timeoffset 1716)] divided by the DRX cycle length 1708.

In some aspects, the wake-up condition may be more successful if the UEskips every second n+1 update. In some aspects, the wake-up conditionmay be more successful if n is updated to n+1 when (10×SFN+subframenumber 1722) modulo (DRX cycle length 1708×specified DRX cycle number1724+specified time offset 1716) is equal to a specified timing value1734. The specified DRX cycle number 1724 may also be referred to as a“specified quantity of DRX cycles.” The specified timing value 1734 maybe a value used for a condition of updating n and may be equal to (DRXcycle length 1708×specified DRX cycle number 1724)−1.

In some aspects, the wake-up condition may account for any SFNwraparound issue. For example, the UE may wake up based at least in parton an SFN wraparound offset 1730. The SFN wraparound offset 1730 may beequal to (10240×m), and m updates to m+1 when the SFN returns to 0(resets to 0 at the start of the next hyper frame). In some aspects, theUE may use the SFN wraparound offset 1730 such that the UE wakes up if(10×SFN+subframe number 1722+SFN wraparound offset 1730) modulo the DRXcycle length 1708 is equal to ((n×specified time offset 1716)+a startingoffset 1728) modulo the DRX cycle length 1708. The UE may update n ton+1 when (10×SFN+subframe number 1722+SFN wraparound offset 1730) modulo(DRX cycle length 1708×specified DRX cycle number 1724+specified timeoffset 1716) is equal to the specified timing value 1734.

The UE may resolve any timing ambiguity of an RRC message. For example,an RRC message may be received later in a hyper frame, past SFN 512, andit may not be clear when the UE is to apply the wake-up condition. Insome aspects, the UE may receive, in an indication (e.g., the RRCmessage) from the network, a DRX time reference SFN 1732. The DRX timereference SFN 1732 may be an SFN that is used to adjust the wake-upcondition to resolve message timing ambiguity. The DRX time referenceSFN 1732 may be SFN 0 or SFN 512. The UE may use the DRX time referenceSFN 1732 to wake up if (10×SFN+subframe number 1722+SFN wraparoundoffset 1730) modulo the DRX cycle length 1728 is equal to [(n×specifiedtime offset 1716)+starting offset 1728+(DRX time reference SFN×10]modulo the DRX cycle length 1708. The UE may update n when(10×SFN+subframe number 1722+SFN wraparound offset 1730) modulo (DRXcycle length 1708×specified DRX cycle number 1724+specified time offset1716) is equal to a specified timing value 1734. The SFN wraparoundoffset 1730 may be 10240×m, where m updates to m+1 when the SFN returnsto the DRX time reference SFN 1732. The DRX time reference SFN 1732 maybe 0 or 512. The UE may receive an indication of the DRX time referenceSFN 1732.

DRX cycle 1706 may be part of an anchor cycle 1738 of multiple DRXcycles, shown by DRX cycles 1702, 1704, 1706, 1740, 1742, and 1744. Theanchor cycle 1738 may include one DRX leap cycle, such as DRX cycle1706. In some aspects, the anchor cycle 1738 may include two or moreleap cycles, such as both DRX cycle 1706 and DRX cycle 1744. The UE mayreceive an indication of the two or more leap cycles. For example, anRRC message may indicate a set of multiple leap cycles (e.g., for 45 HzXR traffic). The indication may indicate a timing of each leap cyclewithin the anchor cycle 1738 or a leap period. The timing may beexplicit, such as a DRX cycle number, an amount of time (e.g., inmilliseconds, slot, and/or symbols with respect to another DRX cycle),an SFN, a subframe number, or a combination thereof.

In some aspects, the UE may use a different wake-up condition, where theUE wakes up based at least in part on the specified time offset 1716added to the on duration 1714 of the DRX cycle 1706 based at least inpart on a DRX cycle number of the DRX cycle 1706 and the DRX timereference SFN 1732. The specified time offset 1716 may be based at leastin part on the periodicity 1726 of the multimedia data bursts, and theDRX cycle number may be based at least in part on the specified timeoffset 1716. For example, the UE may wake up if (SFN×quantity ofsubframes per frame)+subframe number 1722 is equal to [DRX timereference SFN×quantity of subframes per subframe+starting offset1728+DRX on duration number×DRX cycle length 1708+floor (DRX on durationnumber/specified time offset 1716)×specified quantity of DRX cycles]modulo (1024×quantity of subframes per frame).

The DRX on duration number N may be a number of an on duration in theanchor cycle 1738. The DRX on duration number N may correspond to theDRX cycle number. In some aspects, the DRX on duration number N may bethe Nth eCDRX on duration cycle that occurs in the subframe for which[(SFN_M×10)+subframe number 1722] modulo the DRX cycle length1708=modulo the DRX cycle length 1708=[starting offset+(n×specified timeoffset 1716+(DRX time reference SFN×10)] modulo the DRX cycle length1708, where n=n+1 whenever [(SFN_M×10)+subframe number 1722] modulo (DRXcycle length 1708×specified DRX cycle number 1724+specified time offset1716)=(DRX cycle length 1708×specified time offset 1716)−1. Thespecified time offset 1716 may be referred to as a “DRX leap offset.”SFN_M may be the SFN after a modulo operation with a set hyper framelength (in SFNs).

In some aspects, the UE may wake up if [(SFN_M×10)+subframe number 1722]modulo the DRX cycle 1706 is equal to [starting offset+(n×specified timeoffset 1716)+(DRX time reference SFN×10)] modulo the DRX cycle length1708, and where n updates to n+1 when [(SFN_M×10)+subframe number]modulo (DRX cycle length 1708×specified DRX cycle number 1724+specifiedtime offset 1716) is equal to a specified timing value 1734. Thespecified timing value 1734 may be equal to (DRX cycle length1708×specified DRX cycle number 1724)−1.

As indicated above, FIG. 17 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 17 .

FIG. 18 is a diagram illustrating an example 1800 associated with usinga specified time offset, in accordance with the present disclosure. Asshown in FIG. 18 , a network entity 1810 (e.g., base station 110) maycommunicate with a UE 1820 (e.g., UE 120). The network entity 1810 andthe UE 1820 may be part of a wireless network (e.g., wireless network100).

As shown by reference number 1825, the network entity 1810 may transmittraffic bursts according to a periodicity (e.g., video frame rate). Thenetwork entity 1810 may also transmit the data bursts according to awake up condition configured for and used by the UE 1820. As shown byreference number 1830, the UE 1820 may sleep and wake up according toresource cycles and a wake-up condition configured for the UE 1820. Forexample, the UE 1020 may calculate, for each subframe, whetherparameters associated with the UE 1020 and the resource cycle meet thecriteria for waking up. Examples described herein, such as example 1700,show that the resource cycles may be DRX cycles and that the parametersmay be related to the DRX cycles (e.g., SFN, subframe number, DRX cyclelength, DRX cycle number).

However, in some aspects, the wake-up conditions used for DRX may beused for other resources, including a channel state information (CSI)reference signal (CSI-RS), a CSI interference measurement resource(CSI-IM), a sounding reference signal (SRS), a scheduling request (SR),a configured grant (CG) resource, a semi-persistent scheduling (SPS)resource, a CSI report, a buffer status report (BSR), physical downlinkcontrol channel (PDCCH) monitoring, and/or for physical uplink controlchannel (PUCCH) resources.

In some aspects, the network entity 1810 may transmit an indicationassociated with the resource cycle, as shown by reference number 1835.The indication may include parameters (e.g., leap cycle, specified timeoffset) for waking up according to the resource cycles.

In some aspects, the network entity 1810 may prepare for communicationaccording to a DRX cycle, as shown by reference number 1840. This mayinclude determining the DRX cycle that the UE 1820 is to use or otherpreparations for the DRX of the UE 1820. Preparation may includepreparing for a transmission during an on duration of the DRX cycle.

As indicated above, FIG. 18 is provided as an example. Other examplesmay differ from what is described with respect to FIG. 18 .

While aspects are described with respect to multimedia, the aspects mayalso be applied to other applications that involve periodictransmissions.

The mathematic symbols used for wake-up conditions or formulas may beinterpreted to mean similar concepts. For example, a “+” may refer to aplus or addition, a “−” may refer to a minus or subtraction, “x” or “*”may refer to multiplication, and “/” may refer to division.

FIG. 19 is a diagram illustrating an example of a disaggregated basestation 1900, in accordance with the present disclosure.

Deployment of communication systems, such as 5G NR systems, may bearranged in multiple manners with various components or constituentparts. In a 5G NR system, or network, a network node, a network entity,a mobility element of a network, a radio access network (RAN) node, acore network node, a network element, or a network equipment, such as abase station, or one or more units (or one or more components)performing base station functionality, may be implemented in anaggregated or disaggregated architecture. For example, a BS (such as aNode B, evolved NB (eNB), NR BS, 5G NB, access point (AP), a TRP, or acell, etc.) may be implemented as an aggregated base station (also knownas a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocolstack that is physically or logically integrated within a single RANnode. A disaggregated base station may be configured to utilize aprotocol stack that is physically or logically distributed among two ormore units (such as one or more CUs, one or more DUs, or one or moreRUs). In some aspects, a CU may be implemented within a RAN node, andone or more DUs may be co-located with the CU, or alternatively, may begeographically or virtually distributed throughout one or multiple otherRAN nodes. The DUs may be implemented to communicate with one or moreRUs. Each of the CU, DU, and RU also can be implemented as virtual units(e.g., a virtual central unit (VCU), a virtual distributed unit (VDU),or a virtual radio unit (VRU)).

Base station-type operation or network design may consider aggregationcharacteristics of base station functionality. For example,disaggregated base stations may be utilized in an IAB network, an openradio access network (O-RAN (such as the network configuration sponsoredby the O-RAN Alliance)), or a virtualized radio access network (vRAN,also known as a cloud radio access network (C-RAN)).

Disaggregation may include distributing functionality across two or moreunits at various physical locations, as well as distributingfunctionality for at least one unit virtually, which can enableflexibility in network design. The various units of the disaggregatedbase station, or disaggregated RAN architecture, can be configured forwired or wireless communication with at least one other unit.

The disaggregated base station 1900 architecture may include one or moreCUs 1910 that can communicate directly with a core network 1920 via abackhaul link, or indirectly with the core network 1920 through one ormore disaggregated base station units (such as a Near-RT RIC 1925 via anE2 link, or a Non-RT RIC 1915 associated with a Service Management andOrchestration (SMO) Framework 1905, or both). A CU 1910 may communicatewith one or more DUs 1930 via respective midhaul links, such as an F1interface. The DUs 1930 may communicate with one or more RUs 1940 viarespective fronthaul links. The fronthaul link, the midhaul link, andthe backhaul link may be generally referred to as “communication links.”The RUs 1940 may communicate with respective UEs 120 via one or more RFaccess links. In some aspects, the UE 120 may be simultaneously servedby multiple RUs 1940. The DUs 1930 and the RUs 1940 may also be referredto as “O-RAN DUs (O-DUs”) and “O-RAN RUs (O-RUs)”, respectively. Anetwork entity may include a CU, a DU, an RU, or any combination of CUs,DUs, and RUs. A network entity may include a disaggregated base stationor one or more components of the disaggregated base station, such as aCU, a DU, an RU, or any combination of CUs, DUs, and RUs. A networkentity may also include one or more of a TRP, a relay station, a passivedevice, an intelligent reflective surface (IRS), or other componentsthat may provide a network interface for or serve a UE, mobile station,sensor/actuator, or other wireless device.

Each of the units (e.g., the CUs 1910, the DUs 1930, the RUs 1940, aswell as the Near-RT RICs 1925, the Non-RT RICs 1915 and the SMOFramework 1905) may include one or more interfaces or be coupled to oneor more interfaces configured to receive or transmit signals, data, orinformation (collectively, signals) via a wired or wireless transmissionmedium. Each of the units, or an associated processor or controllerproviding instructions to the communication interfaces of the units, canbe configured to communicate with one or more of the other units via thetransmission medium. For example, the units can include a wiredinterface configured to receive or transmit signals over a wiredtransmission medium to one or more of the other units. Additionally, theunits can include a wireless interface, which may include a receiver, atransmitter or transceiver (such as an RF transceiver), configured toreceive or transmit signals, or both, over a wireless transmissionmedium to one or more of the other units.

In some aspects, the CU 1910 may host one or more higher layer controlfunctions. Such control functions can include RRC, packet dataconvergence protocol (PDCP), service data adaptation protocol (SDAP), orthe like. Each control function can be implemented with an interfaceconfigured to communicate signals with other control functions hosted bythe CU 1910. The CU 1910 may be configured to handle user planefunctionality (i.e., Central Unit—User Plane (CU-UP)), control planefunctionality (i.e., Central Unit—Control Plane (CU-CP)), or acombination thereof. In some implementations, the CU 1910 can belogically split into one or more CU-UP units and one or more CU-CPunits. The CU-UP unit can communicate bidirectionally with the CU-CPunit via an interface, such as the E1 interface when implemented in anO-RAN configuration. The CU 1910 can be implemented to communicate withthe DU 1930, as necessary, for network control and signaling.

The DU 1930 may correspond to a logical unit that includes one or morebase station functions to control the operation of one or more RUs 1940.In some aspects, the DU 1930 may host one or more of a radio linkcontrol (RLC) layer, a MAC layer, and one or more high physical (PHY)layers (such as modules for forward error correction (FEC) encoding anddecoding, scrambling, modulation and demodulation, or the like)depending, at least in part, on a functional split, such as thosedefined by the 3GPP. In some aspects, the DU 1930 may further host oneor more low PHY layers. Each layer (or module) can be implemented withan interface configured to communicate signals with other layers (andmodules) hosted by the DU 1930, or with the control functions hosted bythe CU 1910.

Lower-layer functionality can be implemented by one or more RUs 1940. Insome deployments, an RU 1940, controlled by a DU 1930, may correspond toa logical node that hosts RF processing functions, or low-PHY layerfunctions (such as performing fast Fourier transform (FFT), inverse FFT(iFFT), digital beamforming, physical random access channel (PRACH)extraction and filtering, or the like), or both, based at least in parton the functional split, such as a lower layer functional split. In suchan architecture, the RU(s) 1940 can be implemented to handle over theair (OTA) communication with one or more UEs 120. In someimplementations, real-time and non-real-time aspects of control and userplane communication with the RU(s) 1940 can be controlled by thecorresponding DU 1930. In some scenarios, this configuration can enablethe DU(s) 1930 and the CU 1910 to be implemented in a cloud-based RANarchitecture, such as a vRAN architecture.

The SMO Framework 1905 may be configured to support RAN deployment andprovisioning of non-virtualized and virtualized network elements. Fornon-virtualized network elements, the SMO Framework 1905 may beconfigured to support the deployment of dedicated physical resources forRAN coverage requirements which may be managed via an operations andmaintenance interface (such as an O1 interface). For virtualized networkelements, the SMO Framework 1905 may be configured to interact with acloud computing platform (such as an open cloud (O-Cloud) 1990) toperform network element life cycle management (such as to instantiatevirtualized network elements) via a cloud computing platform interface(such as an O2 interface). Such virtualized network elements caninclude, but are not limited to, CUs 1910, DUs 1930, RUs 1940 andNear-RT RICs 1925. In some implementations, the SMO Framework 1905 cancommunicate with a hardware aspect of a 4G RAN, such as an open eNB(O-eNB) 1911, via an O1 interface. Additionally, in someimplementations, the SMO Framework 1905 can communicate directly withone or more RUs 1940 via an O1 interface. The SMO Framework 1905 alsomay include a Non-RT RIC 1915 configured to support functionality of theSMO Framework 1905.

The Non-RT RIC 1915 may be configured to include a logical function thatenables non-real-time control and optimization of RAN elements andresources, Artificial Intelligence/Machine Learning (AI/ML) workflowsincluding model training and updates, or policy-based guidance ofapplications/features in the Near-RT RIC 1925. The Non-RT RIC 1915 maybe coupled to or communicate with (such as via an AI interface) theNear-RT RIC 1925. The Near-RT RIC 1925 may be configured to include alogical function that enables near-real-time control and optimization ofRAN elements and resources via data collection and actions over aninterface (such as via an E2 interface) connecting one or more CUs 1910,one or more DUs 1930, or both, as well as an O-eNB, with the Near-RT RIC1925.

In some implementations, to generate AI/ML models to be deployed in theNear-RT RIC 1925, the Non-RT RIC 1915 may receive parameters or externalenrichment information from external servers. Such information may beutilized by the Near-RT RIC 1925 and may be received at the SMOFramework 1905 or the Non-RT RIC 1915 from non-network data sources orfrom network functions. In some examples, the Non-RT RIC 1915 or theNear-RT RIC 1925 may be configured to tune RAN behavior or performance.For example, the Non-RT RIC 1915 may monitor long-term trends andpatterns for performance and employ AI/ML models to perform correctiveactions through the SMO Framework 1905 (such as reconfiguration via 01)or via creation of RAN management policies (such as AI policies).

As indicated above, FIG. 19 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 19 .

FIG. 20 is a diagram illustrating an example process 2000 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 2000 is an example where the UE (e.g., UE 120, UE 1820) performsoperations associated with a DRX methodology for multimedia.

As shown in FIG. 20 , in some aspects, process 2000 may include sleepingin association with a DRX cycle (block 2010). For example, the UE (e.g.,using communication manager 2608 and/or DRX component 2610 depicted inFIG. 26 ) may sleep in association with a DRX cycle, as described above.

As further shown in FIG. 20 , in some aspects, process 2000 may includewaking up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an on duration of the DRX cycle based atleast in part on a DRX cycle number of the DRX cycle and a length of theDRX cycle, where the specified time offset is based at least in part ona periodicity of multimedia data bursts, and where the DRX cycle numberis based at least in part on the specified time offset (block 2020). Forexample, the UE (e.g., using communication manager 2608 and/or DRXcomponent 2610 depicted in FIG. 26 ) may wake up, starting at asubframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset, as described above.

As further shown in FIG. 20 , in some aspects, process 2000 may includereceiving a multimedia data burst during the subframe (block 2030). Forexample, the UE (e.g., using communication manager 140 and/or receptioncomponent 2602 depicted in FIG. 26 ) may receive a multimedia data burstduring the subframe, as described above.

Process 2000 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the DRX cycle number is equal to [(10×the SFN of aframe comprising the subframe+a subframe number of the subframe)−(n×thespecified time offset)] divided by the length of the DRX cycle.

In a second aspect, alone or in combination with the first aspect,waking up includes waking up if (10×the SFN+the subframe number) modulothe length of the DRX cycle is equal to ((n×the specified time offset)+astarting offset) modulo the length of the DRX cycle, and where n updatesto n+1 when the DRX cycle number modulo a specified quantity of DRXcycles is equal to 0 (zero).

In a third aspect, alone or in combination with one or more of the firstand second aspects, process 2000 includes skipping every second n+1update.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, waking up includes waking up if (10×theSFN+the subframe number) modulo the length of the DRX cycle is equal to((n×the specified time offset)+a starting offset) modulo the length ofthe DRX cycle, and where n updates to n+1 when (10×the SFN+the subframenumber) modulo (the length of the DRX cycle×a specified quantity of DRXcycles+the specified time offset) is equal to a specified timing value.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the specified timing value is equal to (thelength of the DRX cycle×the specified quantity of DRX cycles)−1.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, waking up includes waking up further based atleast in part on an SFN wraparound offset.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, waking up includes waking up if (10×theSFN+the subframe number+the SFN wraparound offset) modulo the length ofthe DRX cycle is equal to ((n×the specified time offset)+a startingoffset) modulo the length of the DRX cycle, and where n updates to n+1when (10×the SFN+the subframe number+the SFN wraparound offset) modulo(the length of the DRX cycle×a specified quantity of DRX cycles+thespecified time offset) is equal to a specified timing value.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the SFN wraparound offset is equal to(10240×m), and m updates to m+1 when the SFN returns to 0 (zero).

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, waking up includes waking up if (10×the SFN+thesubframe number+the SFN wraparound offset) modulo the length of the DRXcycle is equal to [(n×the specified time offset)+a starting offset+(DRXtime reference SFN×10] modulo the length of the DRX cycle, and where nupdates to n+1 when (10×the SFN+the subframe number+the SFN wraparoundoffset) modulo (the length of the DRX cycle×a specified quantity of DRXcycles+the specified time offset) is equal to a specified timing value.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the SFN wraparound offset is 10240×m, where mupdates to m+1 when the SFN returns to the DRX time reference SFN, andthe DRX time reference SFN is 0 or 512.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, process 2000 includes receiving anindication of the DRX time reference SFN.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, an anchor cycle that includes the DRXcycle also includes two or more leap cycles.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, process 2000 includes receiving anindication of the two or more leap cycles.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, process 2000 includes receiving anindication of a timing of the two or more leap cycles. In some aspects,a leap cycle offset pattern of the two or more leap cycles may include(0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).

Although FIG. 20 shows example blocks of process 2000, in some aspects,process 2000 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 20 .Additionally, or alternatively, two or more of the blocks of process2000 may be performed in parallel.

FIG. 21 is a diagram illustrating an example process 2100 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 2100 is an example where the UE (e.g., UE 120, UE 1820) performsoperations associated with a DRX methodology for multimedia.

As shown in FIG. 21 , in some aspects, process 2100 may include sleepingin association with a DRX cycle (block 2110). For example, the UE (e.g.,using communication manager 2608 and/or DRX component 2610 depicted inFIG. 26 ) may sleep in association with a DRX cycle, as described above.

As further shown in FIG. 21 , in some aspects, process 2100 may includewaking up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an on duration of the DRX cycle based atleast in part on a DRX cycle number of the DRX cycle and a DRX timereference SFN, where the specified time offset is based at least in parton a periodicity of multimedia data bursts, and where the DRX cyclenumber is based at least in part on the specified time offset (block2120). For example, the UE (e.g., using communication manager 2608and/or DRX component 2610 depicted in FIG. 26 ) may wake up, starting ata subframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle based at least in part on a DRXcycle number of the DRX cycle and a DRX time reference SFN, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset, as described above.

As further shown in FIG. 21 , in some aspects, process 2100 may includereceiving a multimedia data burst during the subframe (block 2130). Forexample, the UE (e.g., using communication manager 140 and/or receptioncomponent 2602 depicted in FIG. 26 ) may receive a multimedia data burstduring the subframe, as described above.

Process 2100 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, waking up includes waking up if (an SFN of a framecomprising the subframe×a quantity of subframes per frame)+a subframenumber of the subframe is equal to [the DRX time reference SFN×thequantity of subframes per subframe+a starting offset+a DRX on durationnumber×a length of the DRX cycle+floor (the DRX on duration number/thespecified time offset)×a specified quantity of DRX cycles] modulo(1024×the quantity of subframes per frame).

In a second aspect, alone or in combination with the first aspect,waking up includes waking up if [(a modified SFN of a frame comprisingthe subframe×10)+a subframe number of the subframe] modulo a length ofthe DRX cycle is equal to [a starting offset+(n×the specified timeoffset)+(the DRX time reference SFN×10)] modulo the length of the DRXcycle, and where n updates to n+1 when [(SFN_M×10)+the subframe number]modulo (the length of the DRX cycle×a specified quantity of DRXcycles+the specified time offset) is equal to a specified timing value.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the specified timing value is equal to (the lengthof the DRX cycle×the specified quantity of DRX cycles)−1.

Although FIG. 21 shows example blocks of process 2100, in some aspects,process 2100 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 21 .Additionally, or alternatively, two or more of the blocks of process2100 may be performed in parallel.

FIG. 22 is a diagram illustrating an example process 2200 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 2200 is an example where the UE (e.g., UE 120, UE 1820) performsoperations associated with a DRX methodology for multimedia.

As shown in FIG. 22 , in some aspects, process 2200 may include sleepingin association with a resource cycle (block 2210). For example, the UE(e.g., using communication manager 2608 and/or resource component 2612depicted in FIG. 26 ) may sleep in association with a resource cycle, asdescribed above.

As further shown in FIG. 22 , in some aspects, process 2200 may includewaking up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an instance of the resource cycle based atleast in part on a resource cycle number of the resource cycle and alength of the resource cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe resource cycle number is based at least in part on the specifiedtime offset (block 2220). For example, the UE (e.g., using communicationmanager 140 and/or resource component 2612 depicted in FIG. 26 ) maywake up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an instance of the resource cycle based atleast in part on a resource cycle number of the resource cycle and alength of the resource cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe resource cycle number is based at least in part on the specifiedtime offset, as described above.

As further shown in FIG. 22 , in some aspects, process 2200 may includereceiving a multimedia data burst during the subframe (block 2230). Forexample, the UE (e.g., using communication manager 2608 and/or receptioncomponent 2602 depicted in FIG. 26 ) may receive a multimedia data burstduring the subframe, as described above.

Process 2200 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the resource cycle is a cycle for one of a CSIreference signal, a CSI interference measurement resource, or a soundingreference signal.

In a second aspect, alone or in combination with the first aspect, theresource cycle is a cycle for a scheduling request.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the resource cycle is a cycle for a configured grantresource or a semi-persistent scheduling resource.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the resource cycle is a cycle for a channelstate information report or a buffer status report.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the resource cycle is a cycle for physicaldownlink control channel monitoring or for physical uplink controlchannel resources.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the resource cycle number is equal to [(10×asystem frame number (SFN) of a frame comprising the subframe+a subframenumber of the subframe)−(n×the specified time offset)] divided by thelength of the resource cycle.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, waking up includes waking up if (10×theSFN+the subframe number+an SFN wraparound offset) modulo the length ofthe resource cycle is equal to ((n×the specified time offset)+a startingoffset) modulo the length of the resource cycle, and where n updates ton+1 when (10×the SFN+the subframe number+the SFN wraparound offset)modulo (the length of the resource cycle×a specified quantity ofresource cycles+the specified time offset) is equal to a specifiedtiming value.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the SFN wraparound offset is 10240×m, andm updates to m+1 when the SFN returns to 0 (zero).

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, waking up includes waking up if (10×the SFN+thesubframe number+an SFN wraparound offset) modulo the length of theresource cycle is equal to [(n×the specified time offset)+a startingoffset+(a resource time reference SFN×10] modulo the length of theresource cycle, and n updates to n+1 when (10×the resource+the subframenumber+the SFN wraparound offset) modulo (the length of the resourcecycle×a specified quantity of resource cycles+the specified time offset)is equal to a specified timing value.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the SFN wraparound offset is 10240×m, where mupdates to m+1 when the SFN returns to the resource time reference SFN,and the resource time reference SFN is 0 or 512.

Although FIG. 22 shows example blocks of process 2200, in some aspects,process 2200 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 22 .Additionally, or alternatively, two or more of the blocks of process2200 may be performed in parallel.

FIG. 23 is a diagram illustrating an example process 2300 performed, forexample, by a network entity, in accordance with the present disclosure.Example process 2300 is an example where the network entity (e.g., basestation 110, network entity 1810) performs operations associated with aDRX methodology for multimedia.

As shown in FIG. 23 , in some aspects, process 2300 may includepreparing for communication with a UE according to a DRX cycle (block2310). For example, the network entity (e.g., using communicationmanager 2908 and/or DRX component 2910 depicted in FIG. 29 ) may preparefor communication with a UE according to a DRX cycle, as describedabove.

As further shown in FIG. 23 , in some aspects, process 2300 may includetransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a length of the DRX cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset (block 2320). For example, the network entity (e.g., usingcommunication manager 2908 and/or transmission component 2904 depictedin FIG. 29 ) may transmit, starting at a subframe, a data burst based atleast in part on a specified time offset that is added to an on durationof the DRX cycle based at least in part on a DRX cycle number of the DRXcycle and a length of the DRX cycle, where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, andwhere the DRX cycle number is based at least in part on the specifiedtime offset, as described above.

Process 2300 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the DRX cycle number is equal to [(10×SFN of a framecomprising the subframe+a subframe number of the subframe)−(n×thespecified time offset)] divided by the length of the DRX cycle.

In a second aspect, alone or in combination with the first aspect,transmitting the data burst includes transmitting the data burst if(10×the SFN+the subframe number) modulo the length of the DRX cycle isequal to ((n×the specified time offset)+a starting offset) modulo thelength of the DRX cycle, and n updates to n+1 when the DRX cycle numbermodulo a specified quantity of DRX cycles is equal to 0 (zero).

In a third aspect, alone or in combination with one or more of the firstand second aspects, process 2300 includes skipping every second n+1update.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, transmitting the data burst includestransmitting the data burst if (10×the SFN+the subframe number) modulothe length of the DRX cycle is equal to ((n×the specified time offset)+astarting offset) modulo the length of the DRX cycle, and n updates ton+1 when (10×the SFN+the subframe number) modulo (the length of the DRXcycle×a specified quantity of DRX cycles+the specified time offset) isequal to a specified timing value.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the specified timing value is equal to (thelength of the DRX cycle×the specified quantity of DRX cycles)−1.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, transmitting the data burst includes transmittingthe data burst further based at least in part on an SFN wraparoundoffset.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, transmitting the data burst includestransmitting the data burst if (10×the SFN+the subframe number+the SFNwraparound offset) modulo the length of the DRX cycle is equal to((n×the specified time offset)+a starting offset) modulo the length ofthe DRX cycle, and n updates to n+1 when (10×the SFN+the subframenumber+the SFN wraparound offset) modulo (the length of the DRX cycle×aspecified quantity of DRX cycles+the specified time offset) is equal toa specified timing value.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the SFN wraparound offset is equal to(10240×m), and m updates to m+1 when the SFN returns to 0 (zero).

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, transmitting the data burst includestransmitting the data burst up if (10×the SFN+the subframe number+theSFN wraparound offset) modulo the length of the DRX cycle is equal to[(n×the specified time offset)+a starting offset+(DRX time referenceSFN×10] modulo the length of the DRX cycle, and n updates to n+1 when(10×the SFN+the subframe number+the SFN wraparound offset) modulo (thelength of the DRX cycle×a specified quantity of DRX cycles+the specifiedtime offset) is equal to a specified timing value.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the SFN wraparound offset is 10240×m, where mupdates to m+1 when the SFN returns to the DRX time reference SFN, andthe DRX time reference SFN is 0 or 512.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, process 2300 includes transmitting anindication of the DRX time reference SFN.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, an anchor cycle that includes the DRXcycle also includes two or more leap cycles.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, process 2300 includes transmitting anindication of the two or more leap cycles.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, process 2300 includes transmitting anindication of a timing of the two or more leap cycles.

Although FIG. 23 shows example blocks of process 2300, in some aspects,process 2300 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 23 .Additionally, or alternatively, two or more of the blocks of process2300 may be performed in parallel.

FIG. 24 is a diagram illustrating an example process 2400 performed, forexample, by a network entity, in accordance with the present disclosure.Example process 2400 is an example where the network entity (e.g., basestation 110, network entity 1810) performs operations associated with aDRX methodology for multimedia.

As shown in FIG. 24 , in some aspects, process 2400 may includepreparing for communication with a UE according to a DRX cycle (block2410). For example, the network entity (e.g., using communicationmanager 2908 and/or DRX component 2910 depicted in FIG. 29 ) may preparefor communication with a UE according to a DRX cycle, as describedabove.

As further shown in FIG. 24 , in some aspects, process 2400 may includetransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a length of the DRX cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset (block 2420). For example, the network entity (e.g., usingcommunication manager 2908 and/or DRX component 2910 depicted in FIG. 29) may transmit, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a length of the DRX cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset, as described above.

Process 2400 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, transmitting the data burst includes transmitting thedata burst if (an SFN of a frame comprising the subframe×a quantity ofsubframes per frame)+a subframe number of the subframe is equal to [theDRX time reference SFN×the quantity of subframes per subframe+a startingoffset+a DRX on duration number×a length of the DRX cycle+floor (the DRXon duration number/the specified time offset)×a specified quantity ofDRX cycles] modulo (1024×the quantity of subframes per frame).

In a second aspect, alone or in combination with the first aspect,transmitting the data burst includes transmitting the data burst if [(amodified SFN of a frame comprising the subframe×10)+a subframe number ofthe subframe] modulo a length of the DRX cycle is equal to [a startingoffset+(n×the specified time offset)+(the DRX time reference SFN×10)]modulo the length of the DRX cycle, and n updates to n+1 when[(SFN_M×10)+the subframe number] modulo (the length of the DRX cycle×aspecified quantity of DRX cycles+the specified time offset) is equal toa specified timing value.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the specified timing value is equal to (the lengthof the DRX cycle×the specified quantity of DRX cycles)−1.

Although FIG. 24 shows example blocks of process 2400, in some aspects,process 2400 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 24 .Additionally, or alternatively, two or more of the blocks of process2400 may be performed in parallel.

FIG. 25 is a diagram illustrating an example process 2500 performed, forexample, by a network entity, in accordance with the present disclosure.Example process 2500 is an example where the network entity (e.g., basestation 110, network entity 1810) performs operations associated with aDRX methodology for multimedia.

As shown in FIG. 25 , in some aspects, process 2500 may includepreparing for communication with a UE according to a resource cycle(block 2510). For example, the network entity (e.g., using communicationmanager 2908 and/or resource component 2912 depicted in FIG. 29 ) mayprepare for communication with a UE according to a resource cycle, asdescribed above.

As further shown in FIG. 25 , in some aspects, process 2500 may includetransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an instance of theresource cycle based at least in part on a resource cycle number of theresource cycle and a length of the resource cycle, where the specifiedtime offset is based at least in part on a periodicity of multimediadata bursts, and where the resource cycle number is based at least inpart on the specified time offset, and where the resource cycle numberis based at least in part on the specified time offset (block 2520). Forexample, the network entity (e.g., using communication manager 2908and/or transmission component 2904 depicted in FIG. 29 ) may transmit,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an instance of the resource cyclebased at least in part on a resource cycle number of the resource cycleand a length of the resource cycle, where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, wherethe resource cycle number is based at least in part on the specifiedtime offset, and where the resource cycle number is based at least inpart on the specified time offset, as described above.

Process 2500 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the resource cycle is a cycle for one of a CSIreference signal, a CSI interference measurement resource, or a soundingreference signal.

In a second aspect, alone or in combination with the first aspect, theresource cycle is a cycle for a scheduling request.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the resource cycle is a cycle for a configured grantresource or a semi-persistent scheduling resource.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the resource cycle is a cycle for a channelstate information report or a buffer status report.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the resource cycle is a cycle for physicaldownlink control channel monitoring or for physical uplink controlchannel resources.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the resource cycle number is equal to [(10×asystem frame number (SFN) of a frame comprising the subframe+a subframenumber of the subframe)−(n×the specified time offset)] divided by thelength of the resource cycle.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, transmitting the data burst includestransmitting the data burst if (10×the SFN+the subframe number+an SFNwraparound offset) modulo the length of the resource cycle is equal to((n×the specified time offset)+a starting offset) modulo the length ofthe resource cycle, and n updates to n+1 when (10×the SFN+the subframenumber+the SFN wraparound offset) modulo (the length of the resourcecycle×a specified quantity of resource cycles+the specified time offset)is equal to a specified timing value.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the SFN wraparound offset is 10240×m, andm updates to m+1 when the SFN returns to 0 (zero).

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, transmitting the data burst includestransmitting the data burst if (10×the SFN+the subframe number+an SFNwraparound offset) modulo the length of the resource cycle is equal to[(n×the specified time offset)+a starting offset+(a resource timereference SFN×10] modulo the length of the resource cycle, and n updatesto n+1 when (10×the resource+the subframe number+the SFN wraparoundoffset) modulo (the length of the resource cycle×a specified quantity ofresource cycles+the specified time offset) is equal to a specifiedtiming value.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the SFN wraparound offset is 10240×m, where mupdates to m+1 when the SFN returns to the resource time reference SFN,and where the resource time reference SFN is 0 or 512.

Although FIG. 25 shows example blocks of process 2500, in some aspects,process 2500 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 25 .Additionally, or alternatively, two or more of the blocks of process2500 may be performed in parallel.

FIG. 26 is a diagram of an example apparatus 2600 for wirelesscommunication, in accordance with the present disclosure. The apparatus2600 may be a UE (e.g., a UE 120, UE 1820), or a UE may include theapparatus 2600. In some aspects, the apparatus 2600 includes a receptioncomponent 2602 and a transmission component 2604, which may be incommunication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 2600 maycommunicate with another apparatus 2606 (such as a UE, a base station,network entity, or another wireless communication device) using thereception component 2602 and the transmission component 2604. As furthershown, the apparatus 2600 may include the communication manager 140. Thecommunication manager 2608 may control and/or otherwise manage one ormore operations of the reception component 2602 and/or the transmissioncomponent 2604. In some aspects, the communication manager 2608 mayinclude one or more antennas, a modem, a controller/processor, a memory,or a combination thereof, of the UE described in connection with FIG. 2. The communication manager 2608 may be, or be similar to, thecommunication manager 140 depicted in FIGS. 1 and 2 . For example, insome aspects, the communication manager 2608 may be configured toperform one or more of the functions described as being performed by thecommunication manager 140. In some aspects, the communication manager2608 may include the reception component 2602 and/or the transmissioncomponent 2604. The communication manager 2608 may include a DRXcomponent 2610 and/or a resource component 2612, among other examples.

In some aspects, the apparatus 2600 may be configured to perform one ormore operations described herein in connection with FIGS. 1-18 .Additionally, or alternatively, the apparatus 2600 may be configured toperform one or more processes described herein, such as process 2000 ofFIG. 20 , process 2100 of FIG. 21 , process 2200 of FIG. 22 , or acombination thereof. In some aspects, the apparatus 2600 and/or one ormore components shown in FIG. 26 may include one or more components ofthe UE described in connection with FIG. 2 . Additionally, oralternatively, one or more components shown in FIG. 26 may beimplemented within one or more components described in connection withFIG. 2 . Additionally, or alternatively, one or more components of theset of components may be implemented at least in part as software storedin a memory. For example, a component (or a portion of a component) maybe implemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The reception component 2602 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 2606. The reception component2602 may provide received communications to one or more other componentsof the apparatus 2600. In some aspects, the reception component 2602 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus2600. In some aspects, the reception component 2602 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the UE described in connection with FIG. 2 .

The transmission component 2604 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 2606. In some aspects, one or moreother components of the apparatus 2600 may generate communications andmay provide the generated communications to the transmission component2604 for transmission to the apparatus 2606. In some aspects, thetransmission component 2604 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 2606. In some aspects, the transmission component 2604may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described in connection with FIG. 2 . Insome aspects, the transmission component 2604 may be co-located with thereception component 2602 in a transceiver.

In some aspects, the DRX component 2610 may cause the apparatus 2600 tosleep in association with a DRX cycle. The DRX component 2610 may wakethe apparatus 2600 up, starting at a subframe, based at least in part ona specified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.The reception component 2602 may receive a multimedia data burst duringthe subframe.

The reception component 2602 may receive an indication of the DRX timereference SFN, an indication of the two or more leap cycles, and/or anindication of a timing of the two or more leap cycles.

In some aspects, the DRX component 2610 may cause the apparatus 2600 tosleep in association with a DRX cycle. The DRX component 2610 may wakethe apparatus 2600 up, starting at a subframe, based at least in part ona specified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and a DRXtime reference SFN, where the specified time offset is based at least inpart on a periodicity of multimedia data bursts, and where the DRX cyclenumber is based at least in part on the specified time offset. Thereception component 2602 may receive a multimedia data burst during thesubframe.

In some aspects, the resource component 2612 may cause the apparatus2600 to sleep in association with a resource cycle. The resourcecomponent 2612 may wake the apparatus 2600 up, starting at a subframe,based at least in part on a specified time offset that is added to aninstance of the resource cycle based at least in part on a resourcecycle number of the resource cycle and a length of the resource cycle,where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the resource cyclenumber is based at least in part on the specified time offset. Thereception component 2602 may receive a multimedia data burst during thesubframe.

The number and arrangement of components shown in FIG. 26 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 26 . Furthermore, two or more components shownin FIG. 26 may be implemented within a single component, or a singlecomponent shown in FIG. 26 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 26 may perform one or more functions describedas being performed by another set of components shown in FIG. 26 .

FIG. 27 is a diagram illustrating an example 2700 of a hardwareimplementation for an apparatus 2705 employing a processing system 2710.The apparatus 2705 may be a UE (e.g., UE 120, UE 1820).

The processing system 2710 may be implemented with a bus architecture,represented generally by the bus 2715. The bus 2715 may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system 2710 and the overall designconstraints. The bus 2715 links together various circuits including oneor more processors and/or hardware components, represented by theprocessor 2720, the illustrated components, and the computer-readablemedium/memory 2725. The bus 2715 may also link various other circuits,such as timing sources, peripherals, voltage regulators, and/or powermanagement circuits.

The processing system 2710 may be coupled to a transceiver 2730. Thetransceiver 2730 is coupled to one or more antennas 2735. Thetransceiver 2730 provides a means for communicating with various otherapparatuses over a transmission medium. The transceiver 2730 receives asignal from the one or more antennas 2735, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2710, specifically the reception component 2602. Inaddition, the transceiver 2730 receives information from the processingsystem 2710, specifically the transmission component 2604, and generatesa signal to be applied to the one or more antennas 2735 based at leastin part on the received information.

The processing system 2710 includes a processor 2720 coupled to acomputer-readable medium/memory 2725. The processor 2720 is responsiblefor general processing, including the execution of software stored onthe computer-readable medium/memory 2725. The software, when executed bythe processor 2720, causes the processing system 2710 to perform thevarious functions described herein for any particular apparatus. Thecomputer-readable medium/memory 2725 may also be used for storing datathat is manipulated by the processor 2720 when executing software. Theprocessing system further includes at least one of the illustratedcomponents. The components may be software modules running in theprocessor 2720, resident/stored in the computer-readable medium/memory2725, one or more hardware modules coupled to the processor 2720, orsome combination thereof.

In some aspects, the processing system 2710 may be a component of the UE120 and may include the memory 282 and/or at least one of the TX MIMOprocessor 266, the RX processor 258, and/or the controller/processor280. In some aspects, the apparatus 2705 for wireless communicationincludes means for sleeping in association with a DRX cycle and meansfor waking up, starting at a subframe, based at least in part on aspecified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.The apparatus 2705 includes means for receiving a multimedia data burstduring the subframe. In some aspects, the apparatus 2705 includes meansfor sleeping in association with a DRX cycle; means for waking up,starting at a subframe, based at least in part on a specified timeoffset that is added to an on duration of the DRX cycle based at leastin part on a DRX cycle number of the DRX cycle and a DRX time referencesystem frame number (SFN), where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset;and/or means for receiving a multimedia data burst during the subframe.In some aspects, the apparatus 2705 includes means for sleeping inassociation with a resource cycle; means for waking up, starting at asubframe, based at least in part on a specified time offset that isadded to an instance of the resource cycle based at least in part on aresource cycle number of the resource cycle and a length of the resourcecycle, where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the resource cyclenumber is based at least in part on the specified time offset; and/ormeans for receiving a multimedia data burst during the subframe. Theaforementioned means may be one or more of the aforementioned componentsof the apparatus 2600 and/or the processing system 2710 of the apparatus2705 configured to perform the functions recited by the aforementionedmeans. As described elsewhere herein, the processing system 2710 mayinclude the TX MIMO processor 266, the RX processor 258, and/or thecontroller/processor 280. In one configuration, the aforementioned meansmay be the TX MIMO processor 266, the RX processor 258, and/or thecontroller/processor 280 configured to perform the functions and/oroperations recited herein.

FIG. 27 is provided as an example. Other examples may differ from whatis described in connection with FIG. 27 .

FIG. 28 is a diagram illustrating an example 2800 of an implementationof code and circuitry for an apparatus 2805, in accordance with thepresent disclosure. The apparatus 2805 may be a UE (e.g., a UE 120, UE1820), or a UE may include the apparatus 2805.

As shown in FIG. 28 , the apparatus 2805 may include circuitry forsleeping in association with a DRX cycle or a resource cycle (circuitry2820). For example, the circuitry 2820 may enable the apparatus 2805 tosleep in association with a DRX cycle or a resource cycle.

As shown in FIG. 28 , the apparatus 2805 may include, stored incomputer-readable medium 2725, code for sleeping in association with aDRX cycle or a resource cycle (code 2825). For example, the code 2825,when executed by processor 2720, may cause processor 2720 to causetransceiver 2730 to sleep in association with a DRX cycle or a resourcecycle.

As shown in FIG. 28 , the apparatus 2805 may include circuitry forwaking up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an on duration of the DRX cycle (orresource cycle) based at least in part on a DRX cycle (or resourcecycle) number of the DRX cycle (or resource cycle) and a length of theDRX cycle (or resource cycle), where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset (circuitry 2830). For example, the circuitry 2830 may enable theapparatus 2805 to wake up, starting at a subframe, based at least inpart on a specified time offset that is added to an on duration of theDRX cycle (or resource cycle) based at least in part on a DRX cycle (orresource cycle) number of the DRX cycle (or resource cycle) and a lengthof the DRX cycle(or resource cycle), where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, andwhere the DRX cycle (or resource cycle) number is based at least in parton the specified time offset.

As shown in FIG. 28 , the apparatus 2805 may include, stored incomputer-readable medium 2725, code for waking up, starting at asubframe, based at least in part on a specified time offset that isadded to an on duration of the DRX cycle (or resource cycle) based atleast in part on a DRX cycle (or resource cycle) number of the DRX cycle(or resource cycle) and a length of the DRX cycle (or resource cycle),where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle (orresource cycle) number is based at least in part on the specified timeoffset (code 2835). For example, the code 2835, when executed byprocessor 2720, may cause processor 2720 to cause transceiver 2730 towake up, starting at a subframe, based at least in part on a specifiedtime offset that is added to an on duration of the DRX cycle (orresource cycle) based at least in part on a DRX cycle (or resourcecycle) number of the DRX cycle (or resource cycle) and a length of theDRX cycle (or resource cycle), where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle (or resource cycle) number is based at least in part onthe specified time offset.

As shown in FIG. 28 , the apparatus 2805 may include circuitry forreceiving a multimedia data burst during the subframe. For example, thecircuitry 2840 may enable the apparatus 2805 to receive a multimediadata burst during the subframe.

As shown in FIG. 28 , the apparatus 2805 may include, stored incomputer-readable medium 2725, code for receiving a multimedia databurst during the subframe. For example, the code 2845, when executed byprocessor 2720, may cause processor 2720 to cause transceiver 2730 toreceive a multimedia data burst during the subframe.

FIG. 28 is provided as an example. Other examples may differ from whatis described in connection with FIG. 28 .

FIG. 29 is a diagram of an example apparatus 2900 for wirelesscommunication, in accordance with the present disclosure. The apparatus2900 may be a network entity (e.g., base station 110, network entity1810), or a network entity may include the apparatus 2900. In someaspects, the apparatus 2900 includes a reception component 2902 and atransmission component 2904, which may be in communication with oneanother (for example, via one or more buses and/or one or more othercomponents). As shown, the apparatus 2900 may communicate with anotherapparatus 2906 (such as a UE, a base station, or another wirelesscommunication device) using the reception component 2902 and thetransmission component 2904. As further shown, the apparatus 2900 mayinclude the communication manager 2908. The communication manager 2908may control and/or otherwise manage one or more operations of thereception component 2902 and/or the transmission component 2904. In someaspects, the communication manager 2908 may include one or moreantennas, a modem, a controller/processor, a memory, or a combinationthereof, of the network entity described in connection with FIG. 2 . Thecommunication manager 2908 may be, or be similar to, the communicationmanager 150 depicted in FIGS. 1 and 2 . For example, in some aspects,the communication manager 2908 may be configured to perform one or moreof the functions described as being performed by the communicationmanager 150. In some aspects, the communication manager 2908 may includethe reception component 2902 and/or the transmission component 2904. Thecommunication manager 2908 may include a DRX component 2910 and/or aresource component 2912, among other examples.

In some aspects, the apparatus 2900 may be configured to perform one ormore operations described herein in connection with FIGS. 1-18 .Additionally, or alternatively, the apparatus 2900 may be configured toperform one or more processes described herein, such as process 2300 ofFIG. 23 , process 2400 of FIG. 24 , process 2500 of FIG. 25 , or acombination thereof. In some aspects, the apparatus 2900 and/or one ormore components shown in FIG. 29 may include one or more components ofthe network entity described in connection with FIG. 2 . Additionally,or alternatively, one or more components shown in FIG. 29 may beimplemented within one or more components described in connection withFIG. 2 . Additionally, or alternatively, one or more components of theset of components may be implemented at least in part as software storedin a memory. For example, a component (or a portion of a component) maybe implemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The reception component 2902 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 2906. The reception component2902 may provide received communications to one or more other componentsof the apparatus 2900. In some aspects, the reception component 2902 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus2900. In some aspects, the reception component 2902 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the network entity described in connection with FIG. 2 .

The transmission component 2904 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 2906. In some aspects, one or moreother components of the apparatus 2900 may generate communications andmay provide the generated communications to the transmission component2904 for transmission to the apparatus 2906. In some aspects, thetransmission component 2904 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 2906. In some aspects, the transmission component 2904may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the network entity described in connection withFIG. 2 . In some aspects, the transmission component 2904 may beco-located with the reception component 2902 in a transceiver.

In some aspects, the DRX component 2910 may prepare for communicationwith a UE 120 according to a DRX cycle. The transmission component 2904may transmit, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle based at least in part on a DRX cycle number of the DRX cycleand a length of the DRX cycle, where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset.

The transmission component 2904 may transmit an indication of the DRXtime reference SFN, an indication of the two or more leap cycles, and/oran indication of a timing of the two or more leap cycles.

In some aspects, the DRX component 2910 may prepare for communicationwith a UE according to a DRX cycle. The transmission component 2904 maytransmit, starting at a subframe, a data burst based at least in part ona specified time offset that is added to an on duration of the DRX cyclebased at least in part on a DRX cycle number of the DRX cycle and alength of the DRX cycle, where the specified time offset is based atleast in part on a periodicity of multimedia data bursts, and where theDRX cycle number is based at least in part on the specified time offset.

In some aspects, the resource component 2912 may prepare forcommunication with a UE according to a resource cycle. The transmissioncomponent 2904 may transmit, starting at a subframe, a data burst basedat least in part on a specified time offset that is added to an instanceof the resource cycle based at least in part on a resource cycle numberof the resource cycle and a length of the resource cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the resource cycle number is based atleast in part on the specified time offset, and where the resource cyclenumber is based at least in part on the specified time offset.

The number and arrangement of components shown in FIG. 29 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 29 . Furthermore, two or more components shownin FIG. 29 may be implemented within a single component, or a singlecomponent shown in FIG. 29 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 29 may perform one or more functions describedas being performed by another set of components shown in FIG. 29 .

FIG. 30 is a diagram illustrating an example 3000 of a hardwareimplementation for an apparatus 3005 employing a processing system 3010.The apparatus 3005 may be a network entity (e.g., base station 110,network entity 1810).

The processing system 3010 may be implemented with a bus architecture,represented generally by the bus 3015. The bus 3015 may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system 3010 and the overall designconstraints. The bus 3015 links together various circuits including oneor more processors and/or hardware components, represented by theprocessor 3020, the illustrated components, and the computer-readablemedium/memory 3025. The bus 3015 may also link various other circuits,such as timing sources, peripherals, voltage regulators, and/or powermanagement circuits.

The processing system 3010 may be coupled to a transceiver 3030. Thetransceiver 3030 is coupled to one or more antennas 3035. Thetransceiver 3030 provides a means for communicating with various otherapparatuses over a transmission medium. The transceiver 3030 receives asignal from the one or more antennas 3035, extracts information from thereceived signal, and provides the extracted information to theprocessing system 3010, specifically the reception component 2902. Inaddition, the transceiver 3030 receives information from the processingsystem 3010, specifically the transmission component 2904, and generatesa signal to be applied to the one or more antennas 3035 based at leastin part on the received information.

The processing system 3010 includes a processor 3020 coupled to acomputer-readable medium/memory 3025. The processor 3020 is responsiblefor general processing, including the execution of software stored onthe computer-readable medium/memory 3025. The software, when executed bythe processor 3020, causes the processing system 3010 to perform thevarious functions described herein for any particular apparatus. Thecomputer-readable medium/memory 3025 may also be used for storing datathat is manipulated by the processor 3020 when executing software. Theprocessing system further includes at least one of the illustratedcomponents. The components may be software modules running in theprocessor 3020, resident/stored in the computer-readable medium/memory3025, one or more hardware modules coupled to the processor 3020, orsome combination thereof.

In some aspects, the processing system 3010 may be a component of the UE120 and may include the memory 282 and/or at least one of the TX MIMOprocessor 266, the RX processor 258, and/or the controller/processor280. In some aspects, the apparatus 3005 for wireless communicationincludes means for preparing for communication with a UE according to aDRX cycle; and/or means for transmitting, starting at a subframe, a databurst based at least in part on a specified time offset that is added toan on duration of the DRX cycle based at least in part on a DRX cyclenumber of the DRX cycle and a length of the DRX cycle, where thespecified time offset is based at least in part on a periodicity ofmultimedia data bursts, and where the DRX cycle number is based at leastin part on the specified time offset. In some aspects, the apparatus3005 may include means for preparing for communication with a UEaccording to a DRX cycle; and/or means for transmitting, starting at asubframe, a data burst based at least in part on a specified time offsetthat is added to an on duration of the DRX cycle based at least in parton a DRX cycle number of the DRX cycle and a length of the DRX cycle,where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle number isbased at least in part on the specified time offset. In some aspects,the apparatus 3005 may include means for preparing for communicationwith a UE according to a resource cycle; and/or means for transmitting,starting at a subframe, a data burst based at least in part on aspecified time offset that is added to an instance of the resource cyclebased at least in part on a resource cycle number of the resource cycleand a length of the resource cycle, where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, andwhere the resource cycle number is based at least in part on thespecified time offset, and where the resource cycle number is based atleast in part on the specified time offset. The aforementioned means maybe one or more of the aforementioned components of the apparatus 2900and/or the processing system 3010 of the apparatus 3005 configured toperform the functions recited by the aforementioned means. As describedelsewhere herein, the processing system 3010 may include the TX MIMOprocessor 266, the RX processor 258, and/or the controller/processor280. In one configuration, the aforementioned means may be the TX MIMOprocessor 266, the RX processor 258, and/or the controller/processor 280configured to perform the functions and/or operations recited herein.

FIG. 30 is provided as an example. Other examples may differ from whatis described in connection with FIG. 30 .

FIG. 31 is a diagram illustrating an example 3100 of an implementationof code and circuitry for an apparatus 3105, in accordance with thepresent disclosure. The apparatus 3105 may be a network entity (e.g.,base station 110, network entity 1810), or a network entity may includethe apparatus 3105.

As shown in FIG. 31 , the apparatus 3105 may include circuitry forpreparing for communication with a UE according to a DRX cycle or aresource cycle (circuitry 3120). For example, the circuitry 3120 mayenable the apparatus 3105 to prepare for communication with a UEaccording to a DRX cycle or a resource cycle.

As shown in FIG. 31 , the apparatus 3105 may include, stored incomputer-readable medium 3025, code for preparing for communication witha UE according to a DRX cycle or a resource cycle (code 3125). Forexample, the code 3125, when executed by processor 3020, may causeprocessor 3020 to prepare for communication with a UE according to a DRXcycle or a resource cycle.

As shown in FIG. 31 , the apparatus 3105 may include circuitry fortransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle (or resource cycle) based at least in part on a DRX cycle (orresource cycle) number of the DRX cycle (or resource cycle) and a lengthof the DRX cycle (or resource cycle), where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, andwhere the DRX cycle (or resource cycle) number is based at least in parton the specified time offset (circuitry 3130). For example, thecircuitry 3130 may enable the apparatus 3105 to transmit, starting at asubframe, a data burst based at least in part on a specified time offsetthat is added to an on duration of the DRX cycle (or resource cycle)based at least in part on a DRX cycle (or resource cycle) number of theDRX cycle (or resource cycle) and a length of the DRX cycle (or resourcecycle), where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle (orresource cycle) number is based at least in part on the specified timeoffset.

As shown in FIG. 31 , the apparatus 3105 may include, stored incomputer-readable medium 3025, code for transmitting, starting at asubframe, a data burst based at least in part on a specified time offsetthat is added to an on duration of the DRX cycle (or resource cycle)based at least in part on a DRX (or resource cycle) cycle number of theDRX cycle (or resource cycle) and a length of the DRX cycle (or resourcecycle), where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle (orresource cycle) number is based at least in part on the specified timeoffset (code 3135). For example, the code 3135, when executed byprocessor 3020, may cause processor 3020 to cause transceiver 3030 totransmit, starting at a subframe, a data burst based at least in part ona specified time offset that is added to an on duration of the DRX cycle(or resource cycle) based at least in part on a DRX cycle (or resourcecycle) number of the DRX cycle (or resource cycle) and a length of theDRX cycle (or resource cycle), where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle number is based at least in part on the specified timeoffset.

As shown in FIG. 31 , the apparatus 3105 may include circuitry fortransmitting, starting at a subframe, a data burst based at least inpart on a specified time offset that is added to an on duration of theDRX cycle (or resource cycle) based at least in part on a DRX cycle (orresource cycle) number of the DRX cycle (or resource cycle) and a lengthof the DRX cycle (or resource cycle), where the specified time offset isbased at least in part on a periodicity of multimedia data bursts, andwhere the DRX cycle (or resource cycle) number is based at least in parton the specified time offset (circuitry 3130). For example, thecircuitry 3130 may enable the apparatus 3105 to transmit, starting at asubframe, a data burst based at least in part on a specified time offsetthat is added to an on duration of the DRX cycle (or resource cycle)based at least in part on a DRX cycle (or resource cycle) number of theDRX cycle (or resource cycle) and a length of the DRX cycle (or resourcecycle), where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle (orresource cycle) number is based at least in part on the specified timeoffset.

As shown in FIG. 31 , the apparatus 3105 may include, stored incomputer-readable medium 3025, code for transmitting, starting at asubframe, a data burst based at least in part on a specified time offsetthat is added to an on duration of the DRX cycle (or resource cycle)based at least in part on a DRX cycle (or resource cycle) number of theDRX cycle (or resource cycle) and a length of the DRX cycle (or resourcecycle), where the specified time offset is based at least in part on aperiodicity of multimedia data bursts, and where the DRX cycle (orresource cycle) number is based at least in part on the specified timeoffset (code 3135). For example, the code 3135, when executed byprocessor 3020, may cause processor 3020 to cause transceiver 3030 totransmit, starting at a subframe, a data burst based at least in part ona specified time offset that is added to an on duration of the DRX cycle(or resource cycle) based at least in part on a DRX cycle (or resourcecycle) number of the DRX cycle (or resource cycle) and a length of theDRX cycle (or resource cycle), where the specified time offset is basedat least in part on a periodicity of multimedia data bursts, and wherethe DRX cycle (or resource cycle) number is based at least in part onthe specified time offset.

FIG. 31 is provided as an example. Other examples may differ from whatis described in connection with FIG. 31 .

FIG. 32 is a diagram illustrating an example 3200 of leap offsetpatterns, in accordance with the present disclosure.

In some aspects, a configuration may involve multiple DRX cycles. A DRXcycle may be a DRX long cycle. Example 3200 shows DRX long cycles of 16ms for 60 fps XR traffic. Example 3200 shows a DRX start offset of 2 ms.Three DRX cycles total 50 ms.

A DRX cycle may include a DRX leap offset, such as 1 ms. A leap offsetof 1 ms added to the DRX long cycle of 16 ms is a DRX cycle of 17 ms. Insome aspects, a first leap offset pattern 3202 includes a leap offsetpattern of (0 ms, 1 ms, 1 ms). The DRX cycle lengths are thus 16 ms, 17ms, and 17 ms for a total of 50 ms. The first leap offset pattern 3202starts with a DRX cycle of 16 ms and thus the UE is waking up before XRtraffic arrivals. In some aspects, a first leap offset pattern 3204includes a leap offset pattern of (1 ms, 1 ms, 0 ms). The DRX cyclelengths are thus 17 ms, 17 ms, and 16 ms. The first leap offset pattern3204 starts with a DRX cycle of 17 ms and thus the UE is waking up afterXR traffic arrivals. A UE may wake up further based at least in part onan accumulated DRX offset that includes a DRX offset that is equal to aDRX start offset, such as drx-Offset(0)=drx-StartOffset anddrx-Offset(n)=X(n−1)+drx-LeapOffset {(n−1) mod N},m>1. In some aspects,the UE may sequentially search the next nth DRX cycle, and the UE maywake up for a subframe if a subframe index [(SFN×10)+subframenumber]={drx-LongCycle×n+drx-Offset(n)+10×drx-timeReferenceSFN} modulo10240. In some aspects, the UE may sequentially search the next nth DRXcycle, and the UE may wake up for a subframe if(10240×m)+[(SFN×10)+subframe number]{drx-LongCycle×n+drx-Offset(n)+10×drx-timeReferenceSFN} modulo 10240.

As indicated above, FIG. 32 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 32 .

FIG. 33A is a diagram illustrating an example 3300 of subframe indices,in accordance with the present disclosure.

Example 3300 shows a table that includes leap offsets used for subframeindices. The subframe indices may correspond to DRX cycle indices. Forexample, for index n=1, a subframe index ([SFN×10)+subframe number])=16and the leap offset=0. For index n=2, a subframe index=33 and the leapoffset=1. For indexn=3, a subframe index=50 and the leap offset=1. Theleap offset pattern is (0 ms, 1 ms, 1 ms).

As indicated above, FIG. 33A is provided as an example. Other examplesmay differ from what is described with regard to FIG. 33A.

FIG. 33B is a diagram illustrating an example 3302 of subframe indices,in accordance with the present disclosure.

As described in connection with FIG. 15 , a sequential search DRX cycleformula (e.g., for searching the next nth DRX cycle) may involve arational number for drx-ShortCycle, or a DRX cycle. A rational number(e.g., A/B) may represent a non-integer value for drx-ShortCycle. In anexample where drx-ShortCadence=60 fps or 60 Hz (DRX cycles of 16 ms, 16ms, and 17 ms), drx-LongCycle=1000/60=50/3 (16and2Over3). The DRX startoffset may be 0 ms, and the subframe indices may start right before XRdata bursts.

In some aspects, a formula for a non-integer DRX cycle may involve amodulo with a hyper frame length (10240)+a rational number DRX cycle.The formula may include a floor operation that cause the DRX cycle alignwith the subframe granularity (e.g., 1 ms). A ceiling operation may alsobe used instead of a floor operation. The formula may be[(SFN×numberOfSubframesPerFrame)+subframe number in theframe]=[floor(DRX long cycle×n)+the DRX start offset+(10×the DRX timereference SFN] modulo 10240. The number of subframe per frame may be 10,and a DRX time reference SFN may be 0 or 512 (1 bit). Example 3302 inFIG. 33B shows values for subframe indices. The table values may workwhen the subframe index, such as (SFN×10)+subframe number, is greaterthan 10240.

As indicated above, FIG. 33B is provided as an example. Other examplesmay differ from what is described with regard to FIG. 33B.

FIG. 34 is a diagram illustrating an example 3400 of backwardcompatibility, in accordance with the present disclosure.

In some aspects, an enhanced DRX formula solution for the SFN wraparoundproblem, such as adding 10240×m in a DRX formula, may not be compatiblewith a legacy DRX formula for a certain DRX cycles. Some DRX shortcycles may not be compatible with an SFN wraparound solution, such as 3ms, 6 ms, 7 ms, 14 ms, 30 ms, and 35 ms. For example, fordrx-ShortCycle=6 ms (10240/6=1706.6666). DRX long cycles of 60 ms and 70ms may also not be backward compatible. The legacy DRX formula and anenhanced DRX formula work differently under these DRX cycles.

Example 3400 shows a first table 3402 where DRX short cycles havebackward compatibility (“O”) or do not have backward compatibility(“X”). Example 3400 shows a first table 3404 where DRX long cycles havebackward compatibility (“O”) or do not have backward compatibility(“X”).

As indicated above, FIG. 34 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 34 .

FIG. 35 is a diagram illustrating an example 3500 of handling backwardcompatibility, in accordance with the present disclosure.

Example 3500 shows that enhanced UEs, configured to operate with 3GPPstandard Release 18 or later, that can operate using a solution for theSFN wraparound problem and legacy UEs, configured to operate with 3GPPstandard Releases 15-17, that cannot operate using a solution for theSFN wraparound problem. The solution may involve an SFN wraparoundoffset that accounts for accumulated lengths of a hyper frame.

In some aspects, the UE may transmit, in a capability message, anindication of a capability of the UE to use an SFN wrapround offset toaddress the SFN wrapround problem. Enhanced UEs may indicate thecapability, while legacy UEs may not indicate the capability. In someaspects, the indication may be an information element in a capabilitymessage. The UE may receive a legacy DRX configuration that does not usethe SFN wraparound offset or an enhanced DRX configuration that does usethe SFN wraparound offset.

As indicated above, FIG. 35 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 35 .

FIG. 36 is a diagram illustrating an example 3600 associated with usingan SFN wraparound offset, in accordance with the present disclosure. Asshown in FIG. 36 , a network entity 3610 (e.g., base station 110) maycommunicate with a UE 3620 (e.g., UE 120). The network entity 3610 andthe UE 3620 may be part of a wireless network (e.g., wireless network100). The UE 3620 may be an enhanced UE that is capable of using an SFNwrapround offset that accounts for accumulated lengths of a hyper frame.

As shown by reference number 3625, the UE 3620 may transmit, in acapability message, an indication of a capability of the UE 3620 to usethe SFN wrapround offset. As shown by reference number 3630, the networkentity 3610 may transmit, based at least in part on the capabilitymessage, a configuration that uses the SFN wraparound offset (forenhanced UEs).

In some aspects, as shown by reference number 3635, the UE may wake up,starting at a subframe, based at least in part on a subframe index of aresource cycle (e.g., DRX cycle) and an SFN wraparound offset thataccounts for accumulated lengths of a hyper frame. The SFN wraparoundoffset may be equal to a length of the hyper frame×m. The length of thehyper frame may be equal to 10240. As shown by reference number 3640,the UE may receive a data burst (e.g., multimedia data burst) during thesubframe.

In some aspects, the UE 3620 may wake up if the subframe index is for asubframe for which the UE 3620 is to wake up, taking into account theSFN wraparound offset. For example, the UE 3620 may wake up if[(SFN×10)+subframe number+10240×m×k] modulo(drx-ShortCycle)=[(drx-StartOffset(i))+(drx-timeReferenceSFN×10)] modulo(drx-ShortCycle). Since the SFN wraparound offset (10240×m) is activatedfor the UE 3620, the value of k is 1. In some aspects, the value m=m+1whenever the SFN becomes the reference SFN value (drx-timeReferenceSFNis 0 or 512). That is, the subframe index may be equal to [(10×an SFN ofa frame comprising the subframe)+a subframe number of the subframe],where m updates to m+1 when the SFN returns to 0 (zero) or m updates tom+1 when the SFN returns to the time reference SFN, which may be 0 or512. In some aspects, the UE may wake up if (the subframe index+the SFNwraparound offset) modulo a length of the resource cycle is equal to [(astarting offset+(the time reference SFN×10)] modulo the length of theresource cycle. The starting offset may be drx-StartOffset.

In some aspects, the network entity 3610 may transmit an indication ofk=0 and drx-timeReferenceSFN=0 for a legacy DRX operation, and anindication of k=1 for an enhanced DRX operation. By setting k=0, thenetwork entity 3610 may support the legacy UE, and by setting k=1, thenetwork entity may support the enhanced UE for XR. The network entity3610 may set the value k in the configuration, by RRC signaling, DCI, ora MAC CE. In some aspects, m may increase by 1 (m=m+1) when SFN becomesthe time reference SFN value and the network entity 3610 configures theenhanced DRX feature. Otherwise, m may not increase and is fixed to 0(m=0).

In some aspects, the UE 3620 may not alter the enhanced DRX formula, andthe network entity 3610 does not configure the DRX cycles which are notbackward compatible to the legacy UE. For example, the configuration mayindicate for which DRX short cycles and for which DRX long cycles theSFN wraparound offset is applicable or not applicable. The UE 3620 maythen apply the SFN wraparound offset for applicable DRX short cycles andDRX long cycles and not apply the SFN wraparound offset fornon-applicable DRX short cycles and DRX long cycles.

As indicated above, FIG. 36 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 36 .

FIG. 37 is a diagram illustrating an example 3700 of using an SFNwraparound offset, in accordance with the present disclosure.

Example 3700 shows multimedia data burst arrivals that are arriving at arate of 120 Hz. In example 3700, drx-StartOffset is set to 0. A UE mayconfigure a DRX cycle for a cadence of data bursts, such as every 8.33ms at 120 Hz, but the cadence of the data bursts may be associated witha periodicity of 1000 ms. With a multimedia periodicity of 1000 ms and aDRX cycle of 10,240 ms (1024 SFNs per hyper frame at 10 ms each), thehyper frame of the DRX may be misaligned with a frame of a multimediaserver every 10.24 seconds. There is a drift 3702 of 1.666 ms (2 ms inexample 3700) every 10.24 sec (10,240 ms) due to the misalignmentbetween the hyper frame periodicity (10,240 ms) and the multimediaperiodicity. In other words, the hyper frame periodicity (10,240 ms)cannot be divided by the multimedia periodicity (Hz, fps). In an exampleof 120 Hz XR traffic, 10,240 ms/(1000/120) ms=1228.8 frames. Thefractional part of 0.8 (or 1−0.8=0.2) is the remaining partial frame atthe end of the hyper frame, and this partial frame causes an SFNwraparound problem in the next hyper frame. Other multimediaperiodicities result in other quantities of frames that do not alignwith a quantity of SFNs per hyper frame: 45 Hz (460.8 SFNs), 48 Hz(491.52 SFNs), 60 Hz (614.4 SFNs), or 90 Hz (921.6 SFNs.

Example 3700 shows an end of the hyper frame (at SFN 1023) and abeginning of the next hyper frame (at SFN 0), or when the SFN numberswrap around (restart or return to 0) for the next hyper frame. When theend of the hyper frame is reached, an ON-duration wake-up condition orformula, such as (SFN*10)+subframe number=0, may select a subframe foran ON-duration that is between data bursts due to the SFN wraparound.Because the subframe may not be aligned with a data burst, the databurst may not be received. This may cause a degradation ofcommunications that could consume additional processing resources andsignaling.

By adding the SFN wraparound offset 3704 (e.g., the length of the hyperframe (e.g., 1024)×m) to a subframe index 3706 (e.g., (SFN*10)+subframenumber), the subframe 3708 that the UE wakes up at aligns with thecorrect subframe 3710 that matches the burst arrival time of the XRdata. As a result, data is not lost and communications do not degrade.Signaling resources are conserved.

As indicated above, FIG. 37 is provided as an example. Other examplesmay differ from what is described with regard to FIG. 37 .

FIG. 38 is a diagram illustrating an example process 3800 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 3800 is an example where the UE (e.g., UE 120, UE 1820, UE 3620)performs operations associated with DRX.

As shown in FIG. 38 , in some aspects, process 3800 may include wakingup, starting at a subframe, based at least in part on a subframe indexof a resource cycle and an SFN wraparound offset that accounts foraccumulated lengths of a hyper frame (block 3810). For example, the UE(e.g., using communication manager 140 and/or wakeup component 3908,depicted in FIG. 39 ) may wake up, starting at a subframe, based atleast in part on a subframe index of a resource cycle and an SFNwraparound offset that accounts for accumulated lengths of a hyperframe, as described above.

As further shown in FIG. 38 , in some aspects, process 3800 may includereceiving a data burst during the subframe (block 3820). For example,the UE (e.g., using communication manager 140 and/or reception component3902, depicted in FIG. 39 ) may receive a data burst during thesubframe, as described above.

Process 3800 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the SFN wraparound offset is equal to (a length ofthe hyper frame×m).

In a second aspect, alone or in combination with the first aspect, thelength of the hyper frame is equal to 10240.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the subframe index is equal to (10×an SFN of a framecomprising the subframe)+a subframe number of the subframe.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, m updates to m+1 when the SFN returns to 0(zero) or a time reference SFN, and the time reference SFN is 0 or 512.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, waking up includes waking up if (the subframeindex+the SFN wraparound offset) modulo a length of the resource cycleis equal to [(a starting offset+(a time reference SFN×10)] modulo thelength of the resource cycle.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the resource cycle includes a DRX cycle, and thedata burst is a multimedia data burst.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, process 3800 includes transmitting anindication of a capability of using the SFN wraparound offset.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, process 3800 includes activating the SFNwraparound offset.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the SFN wraparound offset is equal to (a lengthof the hyper frame×m×k), where k=1 for activation of the SFN wraparoundoffset k=0 for deactivation of the SFN wraparound offset.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, process 3800 includes receiving a configurationof one or more of DRX short cycles or DRX long cycles that are backwardcompatible for use of the SFN wraparound offset.

Although FIG. 38 shows example blocks of process 3800, in some aspects,process 3800 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 38 .Additionally, or alternatively, two or more of the blocks of process3800 may be performed in parallel.

FIG. 39 is a diagram of an example apparatus 3900 for wirelesscommunication, in accordance with the present disclosure. The apparatus3900 may be a UE (e.g., UE 120, UE 1820, UE 3620), or a UE may includethe apparatus 3900. In some aspects, the apparatus 3900 includes areception component 3902 and a transmission component 3904, which may bein communication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 3900 maycommunicate with another apparatus 3906 (such as a UE, a base station,or another wireless communication device) using the reception component3902 and the transmission component 3904. As further shown, theapparatus 3900 may include the communication manager 140. Thecommunication manager 140 may include one or more of a wakeup component3908, among other examples.

In some aspects, the apparatus 3900 may be configured to perform one ormore operations described herein in connection with FIGS. 17-37 .Additionally, or alternatively, the apparatus 3900 may be configured toperform one or more processes described herein, such as process 3800 ofFIG. 38 . In some aspects, the apparatus 3900 and/or one or morecomponents shown in FIG. 39 may include one or more components of the UEdescribed in connection with FIG. 2 . Additionally, or alternatively,one or more components shown in FIG. 39 may be implemented within one ormore components described in connection with FIG. 2 . Additionally, oralternatively, one or more components of the set of components may beimplemented at least in part as software stored in a memory. Forexample, a component (or a portion of a component) may be implemented asinstructions or code stored in a non-transitory computer-readable mediumand executable by a controller or a processor to perform the functionsor operations of the component.

The reception component 3902 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 3906. The reception component3902 may provide received communications to one or more other componentsof the apparatus 3900. In some aspects, the reception component 3902 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus3900. In some aspects, the reception component 3902 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the UE described in connection with FIG. 2 .

The transmission component 3904 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 3906. In some aspects, one or moreother components of the apparatus 3900 may generate communications andmay provide the generated communications to the transmission component3904 for transmission to the apparatus 3906. In some aspects, thetransmission component 3904 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 3906. In some aspects, the transmission component 3904may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described in connection with FIG. 2 . Insome aspects, the transmission component 3904 may be co-located with thereception component 3902 in a transceiver.

The wakeup component 3908 may wake up, starting at a subframe, based atleast in part on a subframe index of a resource cycle and an SFNwraparound offset that accounts for accumulated lengths of a hyperframe. The reception component 3902 may receive a data burst during thesubframe.

The transmission component 3904 may transmit an indication of acapability of using the SFN wraparound offset. The wakeup component 3908may activate the SFN wraparound offset. The reception component 3902 mayreceive a configuration of one or more of DRX short cycles or DRX longcycles that are backward compatible for use of the SFN wraparoundoffset.

The number and arrangement of components shown in FIG. 39 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 39 . Furthermore, two or more components shownin FIG. 39 may be implemented within a single component, or a singlecomponent shown in FIG. 39 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 39 may perform one or more functions describedas being performed by another set of components shown in FIG. 39 .

FIG. 40 is a diagram illustrating an example 4000 of a hardwareimplementation for an apparatus 4005 employing a processing system 4010.The apparatus 4005 may be a UE (e.g., UE 120, UE 1820, UE 3620).

The processing system 4010 may be implemented with a bus architecture,represented generally by the bus 4015. The bus 4015 may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system 4010 and the overall designconstraints. The bus 4015 links together various circuits including oneor more processors and/or hardware components, represented by theprocessor 4020, the illustrated components, and the computer-readablemedium/memory 4025. The bus 4015 may also link various other circuits,such as timing sources, peripherals, voltage regulators, and/or powermanagement circuits.

The processing system 4010 may be coupled to a transceiver 4030. Thetransceiver 4030 is coupled to one or more antennas 4035. Thetransceiver 4030 provides a means for communicating with various otherapparatuses over a transmission medium. The transceiver 4030 receives asignal from the one or more antennas 4035, extracts information from thereceived signal, and provides the extracted information to theprocessing system 4010, specifically the reception component 3902. Inaddition, the transceiver 4030 receives information from the processingsystem 4010, specifically the transmission component 3904, and generatesa signal to be applied to the one or more antennas 4035 based at leastin part on the received information.

The processing system 4010 includes a processor 4020 coupled to acomputer-readable medium/memory 4025. The processor 4020 is responsiblefor general processing, including the execution of software stored onthe computer-readable medium/memory 4025. The software, when executed bythe processor 4020, causes the processing system 4010 to perform thevarious functions described herein for any particular apparatus. Thecomputer-readable medium/memory 4025 may also be used for storing datathat is manipulated by the processor 4020 when executing software. Theprocessing system further includes at least one of the illustratedcomponents. The components may be software modules running in theprocessor 4020, resident/stored in the computer-readable medium/memory4025, one or more hardware modules coupled to the processor 4020, orsome combination thereof.

In some aspects, the processing system 4010 may be a component of the UE120 and may include the memory 282 and/or at least one of the TX MIMOprocessor 266, the RX processor 258, and/or the controller/processor280. In some aspects, the apparatus 4005 for wireless communicationincludes means for waking up, starting at a subframe, based at least inpart on a subframe index of a resource cycle and an SFN wraparoundoffset that accounts for accumulated lengths of a hyper frame; and/ormeans for receiving a data burst during the subframe. The aforementionedmeans may be one or more of the aforementioned components of theapparatus 2900 and/or the processing system 4010 of the apparatus 4005configured to perform the functions recited by the aforementioned means.As described elsewhere herein, the processing system 4010 may includethe TX MIMO processor 266, the RX processor 258, and/or thecontroller/processor 280. In one configuration, the aforementioned meansmay be the TX MIMO processor 266, the RX processor 258, and/or thecontroller/processor 280 configured to perform the functions and/oroperations recited herein.

FIG. 40 is provided as an example. Other examples may differ from whatis described in connection with FIG. 40 .

FIG. 41 is a diagram illustrating an example 4100 of an implementationof code and circuitry for an apparatus 4105, in accordance with thepresent disclosure. The apparatus 4105 may be a UE, or a UE may includethe apparatus 4105.

As shown in FIG. 41 , the apparatus 4105 may include circuitry forwaking up, starting at a subframe, based at least in part on a subframeindex of a resource cycle and an SFN wraparound offset that accounts foraccumulated lengths of a hyper frame (circuitry 4120). For example, thecircuitry 4120 may enable the apparatus 4105 to wake up, starting at asubframe, based at least in part on a subframe index of a resource cycleand an SFN wraparound offset that accounts for accumulated lengths of ahyper frame.

As shown in FIG. 41 , the apparatus 4105 may include, stored incomputer-readable medium 4025, code for waking up, starting at asubframe, based at least in part on a subframe index of a resource cycleand an SFN wraparound offset that accounts for accumulated lengths of ahyper frame (code 4125). For example, the code 4125, when executed byprocessor 4020, may cause processor 4020 to cause transceiver 4030 towake up, starting at a subframe, based at least in part on a subframeindex of a resource cycle and an SFN wraparound offset that accounts foraccumulated lengths of a hyper frame.

As shown in FIG. 41 , the apparatus 4105 may include circuitry forreceiving a data burst during the subframe (circuitry 4130). Forexample, the circuitry 4130 may enable the apparatus 4105 to receive adata burst during the subframe.

As shown in FIG. 41 , the apparatus 4105 may include, stored incomputer-readable medium 4025, code for receiving a data burst duringthe subframe (code 4135). For example, the code 4135, when executed byprocessor 4020, may cause processor 4020 to cause transceiver 4030 toreceive a data burst during the subframe.

FIG. 41 is provided as an example. Other examples may differ from whatis described in connection with FIG. 41 .

The following provides an overview of some Aspects of the presentdisclosure:

-   -   Aspect 1: A method of wireless communication performed by a user        equipment (UE), comprising: sleeping in association with a        discontinuous reception (DRX) cycle; waking up, starting at a        subframe, based at least in part on a specified time offset that        is added to an on duration of the DRX cycle based at least in        part on a DRX cycle number of the DRX cycle and a length of the        DRX cycle, wherein the specified time offset is based at least        in part on a periodicity of multimedia data bursts, and wherein        the DRX cycle number is based at least in part on the specified        time offset; and receiving a multimedia data burst during the        subframe.    -   Aspect 2: The method of Aspect 1, wherein the DRX cycle number        is equal to [(10×a system frame number (SFN) of a frame        comprising the subframe+a subframe number of the        subframe)−(n×the specified time offset)] divided by the length        of the DRX cycle.    -   Aspect 3: The method of Aspect 2, wherein waking up includes        waking up if (10×the SFN+the subframe number) modulo the length        of the DRX cycle is equal to ((n×the specified time offset)+a        starting offset) modulo the length of the DRX cycle, and wherein        n updates to n+1 when the DRX cycle number modulo a specified        quantity of DRX cycles is equal to 0 (zero).    -   Aspect 4: The method of Aspect 3, further comprising skipping        every second n+1 update.    -   Aspect 5: The method of Aspect 2, wherein waking up includes        waking up if (10×the SFN+the subframe number) modulo the length        of the DRX cycle is equal to ((n×the specified time offset)+a        starting offset) modulo the length of the DRX cycle, and wherein        n updates to n+1 when (10×the SFN+the subframe number) modulo        (the length of the DRX cycle×a specified quantity of DRX        cycles+the specified time offset) is equal to a specified timing        value.    -   Aspect 6: The method of Aspect 5, wherein the specified timing        value is equal to (the length of the DRX cycle×the specified        quantity of DRX cycles)−1.    -   Aspect 7: The method of Aspect 2, wherein waking up includes        waking up further based at least in part on an SFN wraparound        offset.    -   Aspect 8: The method of Aspect 7, wherein waking up includes        waking up if (10×the SFN+the subframe number+the SFN wraparound        offset) modulo the length of the DRX cycle is equal to ((n×the        specified time offset)+a starting offset) modulo the length of        the DRX cycle, and wherein n updates to n+1 when (10×the SFN+the        subframe number+the SFN wraparound offset) modulo (the length of        the DRX cycle×a specified quantity of DRX cycles+the specified        time offset) is equal to a specified timing value.    -   Aspect 9: The method of Aspect 7, wherein the SFN wraparound        offset is equal to (10240×m), and wherein m updates to m+1 when        the SFN returns to 0 (zero).    -   Aspect 10: The method of Aspect 7, wherein waking up includes        waking up if (10×the SFN+the subframe number+the SFN wraparound        offset) modulo the length of the DRX cycle is equal to [(n×the        specified time offset)+a starting offset+(DRX time reference        SFN×10] modulo the length of the DRX cycle, and wherein n        updates to n+1 when (10×the SFN+the subframe number+the SFN        wraparound offset) modulo (the length of the DRX cycle×a        specified quantity of DRX cycles+the specified time offset) is        equal to a specified timing value.    -   Aspect 11: The method of Aspect 10, wherein the SFN wraparound        offset is 10240×m, wherein m updates to m+1 when the SFN returns        to the DRX time reference SFN, and wherein the DRX time        reference SFN is 0 or 512.    -   Aspect 12: The method of Aspect 10, further comprising receiving        an indication of the DRX time reference SFN.    -   Aspect 13: The method of any of Aspects 1-12, wherein an anchor        cycle that includes the DRX cycle also includes two or more leap        cycles.    -   Aspect 14: The method of Aspect 13, further comprising receiving        an indication of the two or more leap cycles.    -   Aspect 15: The method of Aspect 13 or 14, further comprising        receiving an indication of a timing of the two or more leap        cycles.    -   Aspect 16: A method of wireless communication performed by a        user equipment (UE), comprising: sleeping in association with a        discontinuous reception (DRX) cycle; waking up, starting at a        subframe, based at least in part on a specified time offset that        is added to an on duration of the DRX cycle based at least in        part on a DRX cycle number of the DRX cycle and a DRX time        reference system frame number (SFN), wherein the specified time        offset is based at least in part on a periodicity of multimedia        data bursts, and wherein the DRX cycle number is based at least        in part on the specified time offset; and receiving a multimedia        data burst during the subframe.    -   Aspect 17: The method of Aspect 16, wherein waking up includes        waking up if (an SFN of a frame comprising the subframe×a        quantity of subframes per frame)+a subframe number of the        subframe is equal to [the DRX time reference SFN×the quantity of        subframes per subframe+a starting offset+a DRX on duration        number×a length of the DRX cycle+floor (the DRX on duration        number/the specified time offset)×a specified quantity of DRX        cycles] modulo (1024×the quantity of subframes per frame).    -   Aspect 18: The method of Aspect 16, wherein waking up includes        waking up if [(a modified SFN of a frame comprising the        subframe×10)+a subframe number of the subframe] modulo a length        of the DRX cycle is equal to [a starting offset+(n×the specified        time offset)+(the DRX time reference SFN×10)] modulo the length        of the DRX cycle, and wherein n updates to n+1 when        [(SFN_M×10)+the subframe number] modulo (the length of the DRX        cycle×a specified quantity of DRX cycles+the specified time        offset) is equal to a specified timing value.    -   Aspect 19: The method of Aspect 18, wherein the specified timing        value is equal to (the length of the DRX cycle×the specified        quantity of DRX cycles)−1.    -   Aspect 20: A method of wireless communication performed by a        user equipment (UE), comprising: sleeping in association with a        resource cycle; waking up, starting at a subframe, based at        least in part on a specified time offset that is added to an        instance of the resource cycle based at least in part on a        resource cycle number of the resource cycle and a length of the        resource cycle, wherein the specified time offset is based at        least in part on a periodicity of multimedia data bursts, and        wherein the resource cycle number is based at least in part on        the specified time offset; and receiving a multimedia data burst        during the subframe.    -   Aspect 21: The method of Aspect 20, wherein the resource cycle        is a cycle for one of a channel state information (CSI)        reference signal, a CSI interference measurement resource, or a        sounding reference signal.    -   Aspect 22: The method of Aspect 20 or 21, wherein the resource        cycle is a cycle for a scheduling request.    -   Aspect 23: The method of any of Aspects 20-22, wherein the        resource cycle is a cycle for a configured grant resource or a        semi-persistent scheduling resource.    -   Aspect 24: The method of any of Aspects 20-23, wherein the        resource cycle is a cycle for a channel state information report        or a buffer status report.    -   Aspect 25: The method of any of Aspects 20-24, wherein the        resource cycle is a cycle for physical downlink control channel        monitoring or for physical uplink control channel resources.    -   Aspect 26: The method of any of Aspects 20-25, wherein the        resource cycle number is equal to [(10×a system frame number        (SFN) of a frame comprising the subframe+a subframe number of        the subframe)−(n×the specified time offset)] divided by the        length of the resource cycle.    -   Aspect 27: The method of any of Aspects 20-26, wherein waking up        includes waking up if (10×the SFN+the subframe number+an SFN        wraparound offset) modulo the length of the resource cycle is        equal to ((n×the specified time offset)+a starting offset)        modulo the length of the resource cycle, and wherein n updates        to n+1 when (10×the SFN+the subframe number+the SFN wraparound        offset) modulo (the length of the resource cycle×a specified        quantity of resource cycles+the specified time offset) is equal        to a specified timing value.    -   Aspect 28: The method of Aspect 27, wherein the SFN wraparound        offset is 10240×m, and wherein m updates to m+1 when the SFN        returns to 0 (zero).    -   Aspect 29: The method of any of Aspects 20-26, wherein waking up        includes waking up if (10×the SFN+the subframe number+an SFN        wraparound offset) modulo the length of the resource cycle is        equal to [(n×the specified time offset)+a starting offset+(a        resource time reference SFN×10] modulo the length of the        resource cycle, and wherein n updates to n+1 when (10×the        resource+the subframe number+the SFN wraparound offset) modulo        (the length of the resource cycle×a specified quantity of        resource cycles+the specified time offset) is equal to a        specified timing value.    -   Aspect 30: The method of Aspect 29, wherein the SFN wraparound        offset is 10240×m, wherein m updates to m+1 when the SFN returns        to the resource time reference SFN, and wherein the resource        time reference SFN is 0 or 512.    -   Aspect 31: A method of wireless communication performed by a        network entity, comprising: preparing for communication with a        user equipment (UE) according to a discontinuous reception (DRX)        cycle; and transmitting, starting at a subframe, a data burst        based at least in part on a specified time offset that is added        to an on duration of the DRX cycle based at least in part on a        DRX cycle number of the DRX cycle and a length of the DRX cycle,        wherein the specified time offset is based at least in part on a        periodicity of multimedia data bursts, and wherein the DRX cycle        number is based at least in part on the specified time offset.    -   Aspect 32: The method of Aspect 31, wherein the DRX cycle number        is equal to [(10×a system frame number (SFN) of a frame        comprising the subframe+a subframe number of the        subframe)−(n×the specified time offset)] divided by the length        of the DRX cycle.    -   Aspect 33: The method of Aspect 32, wherein transmitting the        data burst includes transmitting the data burst if (10×the        SFN+the subframe number) modulo the length of the DRX cycle is        equal to ((n×the specified time offset)+a starting offset)        modulo the length of the DRX cycle, and wherein n updates to n+1        when the DRX cycle number modulo a specified quantity of DRX        cycles is equal to 0 (zero).    -   Aspect 34: The method of Aspect 33, further comprising skipping        every second n+1 update.    -   Aspect 35: The method of Aspect 32, wherein transmitting the        data burst includes transmitting the data burst if (10×the        SFN+the subframe number) modulo the length of the DRX cycle is        equal to ((n×the specified time offset)+a starting offset)        modulo the length of the DRX cycle, and wherein n updates to n+1        when (10×the SFN+the subframe number) modulo (the length of the        DRX cycle×a specified quantity of DRX cycles+the specified time        offset) is equal to a specified timing value.    -   Aspect 36: The method of Aspect 35, wherein the specified timing        value is equal to (the length of the DRX cycle×the specified        quantity of DRX cycles)−1.    -   Aspect 37: The method of Aspect 32, wherein transmitting the        data burst includes transmitting the data burst further based at        least in part on an SFN wraparound offset.    -   Aspect 38: The method of Aspect 37, wherein transmitting the        data burst includes transmitting the data burst if (10×the        SFN+the subframe number+the SFN wraparound offset) modulo the        length of the DRX cycle is equal to ((n×the specified time        offset)+a starting offset) modulo the length of the DRX cycle,        and wherein n updates to n+1 when (10×the SFN+the subframe        number+the SFN wraparound offset) modulo (the length of the DRX        cycle×a specified quantity of DRX cycles+the specified time        offset) is equal to a specified timing value.    -   Aspect 39: The method of Aspect 37, wherein the SFN wraparound        offset is equal to (10240×m), and wherein m updates to m+1 when        the SFN returns to 0 (zero).    -   Aspect 40: The method of Aspect 37, wherein transmitting the        data burst includes transmitting the data burst up if (10×the        SFN+the subframe number+the SFN wraparound offset) modulo the        length of the DRX cycle is equal to [(n×the specified time        offset)+a starting offset+(DRX time reference SFN×10] modulo the        length of the DRX cycle, and wherein n updates to n+1 when        (10×the SFN+the subframe number+the SFN wraparound offset)        modulo (the length of the DRX cycle×a specified quantity of DRX        cycles+the specified time offset) is equal to a specified timing        value.    -   Aspect 41: The method of Aspect 40, wherein the SFN wraparound        offset is 10240×m, wherein m updates to m+1 when the SFN returns        to the DRX time reference SFN, and wherein the DRX time        reference SFN is 0 or 512.    -   Aspect 42: The method of Aspect 40, further comprising        transmitting an indication of the DRX time reference SFN.    -   Aspect 43: The method of any of Aspects 31-42, wherein an anchor        cycle that includes the DRX cycle also includes two or more leap        cycles.    -   Aspect 44: The method of Aspect 43, further comprising        transmitting an indication of the two or more leap cycles.    -   Aspect 45: The method of Aspect 43 or 44, further comprising        transmitting an indication of a timing of the two or more leap        cycles.    -   Aspect 46: The method of any of Aspects 43-45, wherein a leap        cycle offset pattern of the two or more leap cycles includes (0        milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).    -   Aspect 47: A method of wireless communication performed by a        network entity, comprising: preparing for communication with a        user equipment (UE) according to a discontinuous reception (DRX)        cycle; and transmitting, starting at a subframe, a data burst        based at least in part on a specified time offset that is added        to an on duration of the DRX cycle based at least in part on a        DRX cycle number of the DRX cycle and a length of the DRX cycle,        wherein the specified time offset is based at least in part on a        periodicity of multimedia data bursts, and wherein the DRX cycle        number is based at least in part on the specified time offset.    -   Aspect 48: The method of Aspect 47, wherein transmitting the        data burst includes transmitting the data burst if (an SFN of a        frame comprising the subframe×a quantity of subframes per        frame)+a subframe number of the subframe is equal to [the DRX        time reference SFN×the quantity of subframes per subframe+a        starting offset+a DRX on duration number×a length of the DRX        cycle+floor (the DRX on duration number/the specified time        offset)×a specified quantity of DRX cycles] modulo (1024×the        quantity of subframes per frame).    -   Aspect 49: The method of Aspect 47, wherein transmitting the        data burst includes transmitting the data burst if [(a modified        SFN of a frame comprising the subframe×10)+a subframe number of        the subframe] modulo a length of the DRX cycle is equal to [a        starting offset+(n×the specified time offset)+(the DRX time        reference SFN×10)] modulo the length of the DRX cycle, and        wherein n updates to n+1 when [(SFN_M×10)+the subframe number]        modulo (the length of the DRX cycle×a specified quantity of DRX        cycles+the specified time offset) is equal to a specified timing        value.    -   Aspect 50: The method of Aspect 49, wherein the specified timing        value is equal to (the length of the DRX cycle×the specified        quantity of DRX cycles)−1.    -   Aspect 51: A method of wireless communication performed by a        network entity, comprising: preparing for communication with a        user equipment (UE) according to a resource cycle; and        transmitting, starting at a subframe, a data burst based at        least in part on a specified time offset that is added to an        instance of the resource cycle based at least in part on a        resource cycle number of the resource cycle and a length of the        resource cycle, wherein the specified time offset is based at        least in part on a periodicity of multimedia data bursts, and        wherein the resource cycle number is based at least in part on        the specified time offset, and wherein the resource cycle number        is based at least in part on the specified time offset.    -   Aspect 52: The method of Aspect 51, wherein the resource cycle        is a cycle for one of a channel state information (CSI)        reference signal, a CSI interference measurement resource, or a        sounding reference signal.    -   Aspect 53: The method of Aspect 51 or 52, wherein the resource        cycle is a cycle for a scheduling request.    -   Aspect 54: The method of any of Aspects 51-53, wherein the        resource cycle is a cycle for a configured grant resource or a        semi-persistent scheduling resource.    -   Aspect 55: The method of any of Aspects 51-54, wherein the        resource cycle is a cycle for a channel state information report        or a buffer status report.    -   Aspect 56: The method of any of Aspects 51-55, wherein the        resource cycle is a cycle for physical downlink control channel        monitoring or for physical uplink control channel resources.    -   Aspect 57: The method of any of Aspects 51-56, wherein the        resource cycle number is equal to [(10×a system frame number        (SFN) of a frame comprising the subframe+a subframe number of        the subframe)−(n×the specified time offset)] divided by the        length of the resource cycle.    -   Aspect 58: The method of any of Aspects 51-56, wherein        transmitting the data burst includes transmitting the data burst        if (10×the SFN+the subframe number+an SFN wraparound offset)        modulo the length of the resource cycle is equal to ((n×the        specified time offset)+a starting offset) modulo the length of        the resource cycle, and wherein n updates to n+1 when (10×the        SFN+the subframe number+the SFN wraparound offset) modulo (the        length of the resource cycle×a specified quantity of resource        cycles+the specified time offset) is equal to a specified timing        value.    -   Aspect 59: The method of Aspect 58, wherein the SFN wraparound        offset is 10240×m, and wherein m updates to m+1 when the SFN        returns to 0 (zero).    -   Aspect 60: The method of any of Aspects 51-56, wherein        transmitting the data burst includes transmitting the data burst        if (10×the SFN+the subframe number+an SFN wraparound offset)        modulo the length of the resource cycle is equal to [(n×the        specified time offset)+a starting offset+(a resource time        reference SFN×10] modulo the length of the resource cycle, and        wherein n updates to n+1 when (10×the resource+the subframe        number+the SFN wraparound offset) modulo (the length of the        resource cycle×a specified quantity of resource cycles+the        specified time offset) is equal to a specified timing value.    -   Aspect 61: The method of Aspect 60, wherein the SFN wraparound        offset is 10240×m, wherein m updates to m+1 when the SFN returns        to the resource time reference SFN, and wherein the resource        time reference SFN is 0 or 512.    -   Aspect 62: A method for wireless communication at a user        equipment (UE), comprising: waking up, starting at a subframe,        based at least in part on a subframe index of a resource cycle        and a system frame number (SFN) wraparound offset that accounts        for accumulated lengths of a hyper frame; and receiving a data        burst during the subframe.    -   Aspect 63: The method of Aspect 62, wherein the SFN wraparound        offset is equal to (a length of the hyper frame×m).    -   Aspect 64: The method of any of Aspects 62-63, wherein the        length of the hyper frame is equal to 10240.    -   Aspect 65: The method of any of Aspects 62-64, wherein the        subframe index is equal to (10×an SFN of a frame comprising the        subframe)+a subframe number of the subframe.    -   Aspect 66: The method of Aspect 65, wherein m updates to m+1        when the SFN returns to 0 (zero).    -   Aspect 67: The method of Aspect 65, wherein m updates to m+1        when the SFN returns to a time reference SFN.    -   Aspect 68: The method of Aspect 67, wherein the time reference        SFN is 0 or 512.    -   Aspect 69: The method of any of Aspects 62-68, wherein waking up        includes waking up if (the subframe index+the SFN wraparound        offset) modulo a length of the resource cycle is equal to [(a        starting offset+(a time reference SFN×10)] modulo the length of        the resource cycle.    -   Aspect 70: The method of any of Aspects 62-69, wherein the        resource cycle includes a discontinuous reception (DRX) cycle,        and the data burst is a multimedia data burst.    -   Aspect 71: The method of any of Aspects 62-70, further        comprising transmitting an indication of a capability of using        the SFN wraparound offset.    -   Aspect 72: The method of any of Aspects 62-71, further        comprising activating the SFN wraparound offset.    -   Aspect 73: The method of Aspects 72, wherein the SFN wraparound        offset is equal to (a length of the hyper frame×m×k), where k=1        for activation of the SFN wraparound offset k=0 for deactivation        of the SFN wraparound offset.    -   Aspect 74: The method of any of Aspects 62-73, wherein the one        or more processors are configured to receive a configuration of        one or more of DRX short cycles or DRX long cycles that are        backward compatible for use of the SFN wraparound offset.    -   Aspect 75: An apparatus for wireless communication at a device,        comprising a processor; memory coupled with the processor; and        instructions stored in the memory and executable by the        processor to cause the apparatus to perform the method of one or        more of Aspects 1-74.    -   Aspect 76: A device for wireless communication, comprising a        memory and one or more processors coupled to the memory, the one        or more processors configured to perform the method of one or        more of Aspects 1-74.    -   Aspect 77: An apparatus for wireless communication, comprising        at least one means for performing the method of one or more of        Aspects 1-74.    -   Aspect 78: A non-transitory computer-readable medium storing        code for wireless communication, the code comprising        instructions executable by a processor to perform the method of        one or more of Aspects 1-74.    -   Aspect 79: A non-transitory computer-readable medium storing a        set of instructions for wireless communication, the set of        instructions comprising one or more instructions that, when        executed by one or more processors of a device, cause the device        to perform the method of one or more of Aspects 1-74.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware and/or a combination of hardware and software. “Software”shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,and/or functions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a “processor” is implemented in hardwareand/or a combination of hardware and software. It will be apparent thatsystems and/or methods described herein may be implemented in differentforms of hardware and/or a combination of hardware and software. Theactual specialized control hardware or software code used to implementthese systems and/or methods is not limiting of the aspects. Thus, theoperation and behavior of the systems and/or methods are describedherein without reference to specific software code, since those skilledin the art will understand that software and hardware can be designed toimplement the systems and/or methods based, at least in part, on thedescription herein.

As used herein, “satisfying a threshold” may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. Many of thesefeatures may be combined in ways not specifically recited in the claimsand/or disclosed in the specification. The disclosure of various aspectsincludes each dependent claim in combination with every other claim inthe claim set. As used herein, a phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination withmultiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b,a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b,and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items andmay be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” or the like are intendedto be open-ended terms that do not limit an element that they modify(e.g., an element “having” A may also have B). Further, the phrase“based on” is intended to mean “based, at least in part, on” unlessexplicitly stated otherwise. Also, as used herein, the term “or” isintended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (e.g.,if used in combination with “either” or “only one of”).

What is claimed is:
 1. An apparatus for wireless communication at a userequipment (UE), comprising: a memory; and one or more processors,coupled to the memory, configured to: wake up the apparatus starting ata subframe, based at least in part on a specified time offset that isadded to an on duration of a discontinuous reception (DRX) cycle basedat least in part on a DRX cycle number of the DRX cycle and a length ofthe DRX cycle, wherein the specified time offset is based at least inpart on a periodicity of multimedia data bursts, and wherein the DRXcycle number is based at least in part on the specified time offset; andreceive a multimedia data burst during the subframe.
 2. The apparatus ofclaim 1, wherein the DRX cycle number is equal to [(10×a system framenumber (SFN) of a frame comprising the subframe+a subframe number of thesubframe)−(n×the specified time offset)] divided by the length of theDRX cycle.
 3. The apparatus of claim 2, wherein the one or moreprocessors, to wake up the apparatus, are configured to wake up theapparatus further based at least in part on an SFN wraparound offset. 4.The apparatus of claim 3, wherein the SFN wraparound offset is equal to(10240×m), and wherein m updates to m+1 when the SFN returns to 0(zero).
 5. The apparatus of claim 3, wherein the one or more processors,to wake up the apparatus, are configured to wake up the apparatus if(10×the SFN+the subframe number+the SFN wraparound offset) modulo thelength of the DRX cycle is equal to [(n×the specified time offset)+astarting offset+(DRX time reference SFN×10] modulo the length of the DRXcycle, and wherein n updates to n+1 when (10×the SFN+the subframenumber+the SFN wraparound offset) modulo (the length of the DRX cycle×aspecified quantity of DRX cycles+the specified time offset) is equal toa specified timing value.
 6. The apparatus of claim 5, wherein the SFNwraparound offset is 10240×m, wherein m updates to m+1 when the SFNreturns to the DRX time reference SFN, and wherein the DRX timereference SFN is 0 or
 512. 7. The apparatus of claim 5, wherein the oneor more processors are configured to receive an indication of the DRXtime reference SFN.
 8. The apparatus of claim 1, wherein an anchor cyclethat includes the DRX cycle also includes two or more leap cycles. 9.The apparatus of claim 8, wherein the one or more processors areconfigured to receive an indication of the two or more leap cycles or anindication of a timing of the two or more leap cycles.
 10. The apparatusof claim 8, wherein a leap cycle offset pattern of the two or more leapcycles includes (0 milliseconds (ms), 1 ms, 1 ms) or (1 ms, 1 ms, 0 ms).11. An apparatus for wireless communication at a user equipment (UE),comprising: a memory; and one or more processors, coupled to the memory,configured to: wake up the apparatus, starting at a subframe, based atleast in part on a specified time offset that is added to an on durationof a discontinuous reception (DRX) cycle based at least in part on a DRXcycle number of the DRX cycle and a DRX time reference system framenumber (SFN), wherein the specified time offset is based at least inpart on a periodicity of multimedia data bursts, and wherein the DRXcycle number is based at least in part on the specified time offset; andreceive a multimedia data burst during the subframe.
 12. The apparatusof claim 11, wherein the one or more processors, to wake up theapparatus, are configured to wake up the apparatus if (an SFN of a framecomprising the subframe×a quantity of subframes per frame)+a subframenumber of the subframe is equal to [the DRX time reference SFN×thequantity of subframes per subframe+a starting offset+a DRX on durationnumber×a length of the DRX cycle+floor (the DRX on duration number/thespecified time offset)×a specified quantity of DRX cycles] modulo(1024×the quantity of subframes per frame).
 13. An apparatus forwireless communication at a user equipment (UE), comprising: a memory;and one or more processors, coupled to the memory, configured to: wakeup the apparatus, starting at a subframe, based at least in part on aspecified time offset that is added to an instance of a resource cyclebased at least in part on a resource cycle number of the resource cycleand a length of the resource cycle, wherein the specified time offset isbased at least in part on a periodicity of multimedia data bursts, andwherein the resource cycle number is based at least in part on thespecified time offset; and receive a multimedia data burst during thesubframe.
 14. The apparatus of claim 13, wherein the resource cycle is acycle for one of a channel state information (CSI) reference signal, aCSI interference measurement resource, or a sounding reference signal.15. The apparatus of claim 13, wherein the resource cycle is a cycle fora scheduling request.
 16. The apparatus of claim 13, wherein theresource cycle is a cycle for a configured grant resource or asemi-persistent scheduling resource.
 17. The apparatus of claim 13,wherein the resource cycle is a cycle for a channel state informationreport or a buffer status report.
 18. The apparatus of claim 13, whereinthe resource cycle is a cycle for physical downlink control channelmonitoring or for physical uplink control channel resources.
 19. Theapparatus of claim 13, wherein the one or more processors, to wake upthe apparatus, are configured to wake up the apparatus if (10××a systemframe number (SFN) of a frame comprising the subframe+a subframe numberof the subframe+an SFN wraparound offset) modulo the length of theresource cycle is equal to ((n×the specified time offset)+a startingoffset) modulo the length of the resource cycle, wherein n updates ton+1 when (10×the SFN+the subframe number+the SFN wraparound offset)modulo (the length of the resource cycle×a specified quantity ofresource cycles+the specified time offset) is equal to a specifiedtiming value, and wherein the SFN wraparound offset is 10240×m, andwherein m updates to m+1 when the SFN returns to 0 (zero).
 20. Anapparatus for wireless communication at a user equipment (UE),comprising: a memory; and one or more processors, coupled to the memory,configured to: wake up, starting at a subframe, based at least in parton a subframe index of a resource cycle and a system frame number (SFN)wraparound offset that accounts for accumulated lengths of a hyperframe; and receive a data burst during the subframe.
 21. The apparatusof claim 20, wherein the SFN wraparound offset is equal to (a length ofthe hyper frame×m).
 22. The apparatus of claim 21, wherein the length ofthe hyper frame is equal to
 10240. 23. The apparatus of claim 21,wherein the subframe index is equal to (10×an SFN of a frame comprisingthe subframe)+a subframe number of the subframe.
 24. The apparatus ofclaim 23, wherein m updates to m+1 when the SFN returns to 0 (zero) or atime reference SFN, and wherein the time reference SFN is 0 or
 512. 25.The apparatus of claim 20, wherein the one or more processors, to wakeup, are configured to wake up if (the subframe index+the SFN wraparoundoffset) modulo a length of the resource cycle is equal to [(a startingoffset+(a time reference SFN×10)] modulo the length of the resourcecycle.
 26. The apparatus of claim 20, wherein the resource cycleincludes a discontinuous reception (DRX) cycle, and the data burst is amultimedia data burst.
 27. The apparatus of claim 20, wherein the one ormore processors are configured to transmit an indication of a capabilityof using the SFN wraparound offset.
 28. The apparatus of claim 20,wherein the one or more processors are configured to activate the SFNwraparound offset.
 29. The apparatus of claim 20, wherein the SFNwraparound offset is equal to (a length of the hyper frame×m×k), wherek=1 for activation of the SFN wraparound offset k=0 for deactivation ofthe SFN wraparound offset.
 30. The apparatus of claim 20, wherein theone or more processors are configured to receive a configuration of oneor more of DRX short cycles or DRX long cycles that are backwardcompatible for use of the SFN wraparound offset.